> > It would almost be better to fork the message handling after the rcpt
> > phase and effectively do a single delivery for each rcpt.
On the other hand: In a per-user config environment it might make sense to
do not have any configuration dependant datapost plugin (like spamassassin
or clamav) at all, but do the filtering in local delivery. I will probably
go that way anyway, because i want to allow my customers to choose between
'accept', 'drop' and a third case: 'move into a "probably spam" folder'.
For this i will likely also modify the dnsbl and rhsbl to be able to tag
the mail in headers instead of rejecting it (depending on user configuration).
-kju
--
It's an insane world, but i'm proud to be a part of it. -- Bill Hicks
