On Mon Jan 05, 2009 at 10:56:42 -0500, Chris Lewis wrote: > Eg: We hold off issuing 550s until the DATA transaction completes. This > means that all filtering plugins have have a mutually agreed to place to > stick their results, know what to check before wasting time on redundant > filtering when the choice has already been made, and _always_ return > DECLINED. Logging knows about this, and generates an easily parsed log > record. Quarantine and forwarding all know, and do the right thing. > There's only one return DENY in the entire plugin set (well, three, > including the "we don't relay" and "no such user" returns). > > The entire filtering suite is configurable/switchable by per-domain (and > potentially per recipient) config.
Careful, I'll not be able to sell my service if all that stuff becomes common-place ;) Although I suspect that doing this in a very general purpose manner would be pretty hard. The basics such as "is the domain local" would be easy enough, but the per-user, and per-domain flags for different things would be trickier to handle. Both in terms of configuration and in storage. I'd be happy to document some of my choices, if there were interest. But I again I suspect they'd not be too useful to other people. Steve -- Managed Anti-Spam Service http://mail-scanning.com/
