Recent content by ivenae

I wrote a lot about filtertuning in this thread: https://forum.proxmox.com/threads/installation-advisory.182175/

I wrote very lot about custom filter and how to define them in this thread. https://forum.proxmox.com/threads/installation-advisory.182175/

Mich würde interessieren, welche Filterquoten in etwa erreicht werden und an welchen Stellen die Mails hängen bleiben (DNSBL, Spamassassin, Blocklist, ...) Welche Mails machen euch am meisten Probleme? Bei mir sind etwa 50% DNSBL 35% Postfix-Addon (Policyguard) 10% Spamassassin 5 % kommen...

I just reject them temporarily with my policyguard. If the error is a temp error, it will arrive approx. 5 min later. If it was spam (and the sender dns is missconfigured), there is mostly no second try...

Ask Claude Opus, it maybe can help you. I already solved a few things with AI

Als großzügiger Nutzer von No Subscription muss ich leider sagen, dass ich halt einfach mit so etwas leben muss. Ich mache die Updates monatlich (automatisiert) und starte nur ca. 1/4 der Kisten in der gleichen Nacht neu, die anderen warten 24 Stunden. Dann hab ich noch genügend Zeit zu...

Theoretically you could add it with a block to senderaccess. But senderaccess is overwritten by proxmox regularly and you can only add whitelist domains via PMG Mailproxy -> Welcomelist You have to use the Mail Filter -> Who Object -> Blocklist as MKle explained.

Zwei Kommentare dazu: - Leider hat SRS bei mir das Problem nicht wirklich gelöst. Mein Ziel hat (eine Zeit lang) DMARC Verstöße gegreylistet. Die Anzahl der Greylistings ist durch SRS nicht zurückgegangen. Also ja: SPF Probleme bekommt ihr damit in den Griff. Aber wenn nach DMARC Verstößen...

2026-05-07T10:19:34.783500+02:00 mx pmg-smtp-filter[737784]: 4C31AF69FC4B13AA391: accept mail to <********************> (9B57D4C31BB) (rule: default-accept) This domain is not on your blocklist, or the blocklist action rule is deactivated.

Install the policydaemon from the second post. This should resolve most of your google problems. If you have any questions, ask your questions beneath this forum post. https://forum.proxmox.com/threads/block-google-groups-firebasemail-firebaseapp-googleusercontent-com-in-postfix-before-data.181674/

Introduction Proxmox Mail Gateway has no built-in action to rewrite the mail body — it can block, quarantine or tag mails, but it cannot neutralise links in suspicious messages. This howto shows how to add a custom Defang action module that rewrites http:// and https:// URLs to hxxp:// /...

I like to rewrite the entire body, especially emedded e-mail links so you cannot click them anymore. Edit: Done https://forum.proxmox.com/threads/rewrite-urls-in-mail-bodies-based-on-spamassassin-score.183365/

Das Greylisting Feature des PMG ist leider nicht schön gelöst – rspamd löst es wesentlich besser, weil E-Mails nur dann greylisted werden, wenn sie eine hohe Spamwahrscheinlichkeit haben, während PMG neue Adressen grundsätzlich greylisted. Meine Hoffnung ist ja, dass PMG das auch bald kann...

Yes. The last version do spf check and need therefore more mandatory parameter to work (which postfix will transmit, but you didn't) Sorry i didn't explain that. helo_name=google.com sender=bla@firebaseapp.com client_address=8.8.8.8 client_name=mail.google.com < new line > spf-policy...

This is normal in the default setup. The default settings are generally very conservative, so you may need to adjust some of your scores under "Spam Detector" -> "Custom Scores" (don’t forget to click Apply). You can search for filters in the Tracking Center and look for ones that identify only...