Daniele Nicolodi wrote:
Hello Kris, thank you for your comments.

On 18/10/11 17:03, Kris Deugau wrote:
Since you're happy to deliver the spam somewhere, rather than trying to
reject it during the SMTP conversation, you're probably best off calling
spamc early in your local-delivery rules rather than trying to integrate
it into Postfix somewhere.  This way mail for a given real recipient
will always get processed by that recipient's filtering rules.

Well, I would very happy to discard spam as early as possible, however,
as I understand it, I can run Spamassassin rules only once the full
message in received, and therefore there is little value in having it
rejected sooner or later. What would be the solution to have it rejected
sooner than what is happening with my current configuration?

I don't know exactly how you'd do it, but IIRC the minimum change would be to configure Postfix to send a 550 error if the SA score is beyond a certain point. You still incur the bandwidth cost to receive the data, but you don't have to store the messages you reject.

I think this is possible without any other software, but for flexibility and better control you'd probably want to switch to a content filter or milter that can call SA.

Personally, for inbound mail I prefer to run SA on delivery more or less as described in the SA procmail example, and deliver it all (mostly to one or another spam folders).

Look up the standard procmailrc example from the SpamAssassin docs, and
adapt as necessary for sieve.

Sieve can not call external programs, therefore I do not know ho to hook
Spamassassin there, and, furthermore, I would like to avoid to have to
setup things for each user.

O_o News to me. Maybe there's some option to do this in dovecot-lda? Is there a global sieve configuration similar to /etc/procmailrc? I don't use either so I can't really suggest anything else that wouldn't be a big change in your mail processing.

-kgd

Reply via email to