Hi,
Thomas Hochstein wrote:
Cole Tuininga schrieb:
When an email comes in for a particular user, I'd like it to be
processed through Spam Assassin, using that particular user's
preferences. As I understand it, that mostly gets rid of the idea of
using an ACL to do it.
Then do it the old way: set up a transport to pipe the mail through
spamc and back to Exim, then route all (incoming) mail through that
filter:
<http://dman13.dyndns.org/~dman/config_docs/exim-spamassassin/node12.html>
Worked for me for some years (first with SpamAssassin alone, then with
amavisd-new).
We're about to do the same, but since mail is delivered to another
machine with SMTP (or eventually with LMTP with a transport that looks
roughly the same) we have "no loop". Don't know if this is usefull, but
this is my transport:
scan_smtp:
driver = smtp
# would use batch_max = 1 here with pipe or lmtp
max_rcpt = 1
serialize_hosts = *
transport_filter = /usr/local/bin/spamc -u $local_part
size_addition = -1
rcpt_include_affixes = true
In my test-setup this seems to work nicely with per-user preferences
stored in SQL,
(if anyone sees a downside to this approach instead of the pipe (unless
for that being usable in more situations)...)
Paul
--
## List details at http://www.exim.org/mailman/listinfo/exim-users
## Exim details at http://www.exim.org/
## Please use the Wiki with this list - http://www.exim.org/eximwiki/
