3. In exim make router that check if X_Spam_Kill exists and
move mail to /dev/null.
As Matus already mentioned, don't plain drop it. SMTP reject is proper
handling.
On 20.07.14 10:52, Adi wrote:
Yes SMTP reject is proper. And normally is can be done in ACL by
"deny" options.
But I must do it probably much later in router/transport.
Because my configuration is different: for each recipient pipe
spamc and pipe additional process exim to Mailbox.
Have you tried the amavis/sa-exim way?
Some my configuration is based on:
http://www.janoszen.com/2013/07/24/filtering-spam-with-exim-and-spamassassin-properly/
I looked onto that and did not like it. Mostly because it does not run at
the SMTP time...
In normal Exim's configuration mail will be analized by SA only once
(only for TO: address - I must check if all user prefs is readed and
used in this case).
So, I can:
1. not worry about the messages with multiple recipients
and use simple building ACL options in Exim. Fast and easy to
configure.
2. try do it properly for multiple recipients mails. But there are
many problems. Is slower, hard to configure (example reject email:)
you can do two checks, one at SMTP time (with sane defaults), and second
(user-personalized) at delivery time.
single recipient e-mails can be scanned with user preferences at SMTP time
and you can skip the latter step for them.
Of course, spam rejected at SMTP time won't be scanned with per-user
settings...
--
Matus UHLAR - fantomas, [email protected] ; http://www.fantomas.sk/
Warning: I wish NOT to receive e-mail advertising to this address.
Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
Fucking windows! Bring Bill Gates! (Southpark the movie)
