Re: Chain content filters in Postfix

[Reindl Harald]

Am 10.03.2015 um 23:39 schrieb Roger Walters:

Hello,

I have my Postfix configured so smtp is filtered by SpamAssassin:

     smtp      inet  n       -       -       -       -       smtpd -o
content_filter=spamassassin

spamassassin unix       -       n       n       -       -       pipe
   user=debian-spamd argv=/usr/bin/spamc -f -e /usr/bin/python
/opt/another_filter.py

So my aim is to make that the result of SpamAssassin is not directly
injected back to Postfix again but it should be processed by another
pipe filter instead

you maybe better served by running as milter

* that way there is no re-inject at all
* the first milter with a reject stops the processing
* you can use withelist and OK restricitions without bypass contentfilters

smtpd_milters = unix:/run/spamass-milter/spamass-milter.sock, unix:/run/clamav-milter/clamav-milter.socket the reason why clamav is running here after SA is because SA rejects most malware mails and finally a lot more than clamav so for the majority of spam/malware mails only one filter is running (even the fact that clamav is faster in prcoessing it safes ressources)

signature.asc
Description: OpenPGP digital signature