On Sun, 1 Dec 2002, Jay Maynard wrote:

> I've installed Postfix 1.1.11 and SpamAssassin 2.43. Currently, SA is set up
> in the standard way, as a content filter during delivery. I'd like to use it
> instead to provide the same capabilities as the header_checks and
> body_checks configuration parameters, to allow rejection of spam during the
> data transfer phase of the SMTP transaction instead of depending on the
> (highly unreliable) ability to bounce the message after the spam is accepted
> for delivery. Has anyone done this, or can it be done?

This is not such a good idea. The solution would be to put SpamaAssassin
in front of postfix, and that would hobble postfix to a large extent.
That means that, basically, none of the smtpd_*_checks can be used. You
can't reject based on client, because SpamAssassin would be the program
forwarding email to postfix. You can't reject based on sender or
recipient address, because what is SpamAssassin supposed to do with the
rejected email? You can't use any of the RBLs, because the client is long
gone by the time SpamAssassin finishes with the message and gives it to
postfix.

Run Amavisd-new as the content filter, which calls SpamAssassin. Have it
simply drop rejected email, if you want, but let postfix do its job,
first.

----
Russell Mosemann, Ph.D. * Computing Services * Concordia University, Nebraska
"You can't make me do it."  "True, but I can make you wish you had."
 - David Dolak recounting an exchange from his teaching experiences

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]