Re: spamassassin after tmda ?

"Sam Ami" <[email protected]> writes:

> hi all
>
> i'm using spamassassin as well as tmda (don't ask) and would like to
> know if anyone knows how to scan email after the tmda process, not
> before as is the case with a default setup with qmail, qmail-scanner
> and spamassassin

If you use the '-p' or '--print' option on the command line of
tmda-filter, the email will not be delivered, but rather, it will end up
being piped to stdout with an appropriate error code:

  -p, --print     Print the message to stdout.  This option is useful
                  when TMDA is run as a filter in maildrop or procmail.
                  It overrides all other delivery options, even if a
                  specific delivery is given in a matching rule. If the
                  message is delivered, TMDA's exit code is 0.  If the
                  message is dropped, bounced or a confirmation request
                  is sent, the exit code will be 99.  You can use the
                  exit code in maildrop/procmail to decide if you want to
                  perform further processing.

You can set up a procmail or maildrop recipe to pipe your email through
'tmda-filter -p', and then based on the error code, you can then pipe it
again through spamassassin.

Will this give you what you want?


-- 
 Lloyd Zusman
 [email protected]
 God bless you.