On 03/10/2015 11:39 PM, Roger Walters wrote:
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.

If the second script (another_filter.py) determines that the e-mail is OK,
there's no problem with injecting it via the sendmail command.

However, if the second filter determines that the message should be
rejected, it should propagate that state back to SpamAssassin and be the
latter who tells Postfix the final status.

I don't know how to make SpamAssassin collect the status of the
another_filter.py filter and act accordingly. Could someone shed some light
on this?


I'd use some real glue instead direct Postfix pipes to spamc.

amavisd-new or even better Fuglu (in Python) which has a plugin framework so you can insert your "another_filter.py" into the flow, wherever you want it and feed the results back into SA via pseudo headers, etc.

http://fuglu.org/

Docs on
http://gryphius.github.io/fuglu/
http://gryphius.github.io/fuglu/plugins-index.html

h2h

Axb

Reply via email to