Lorenzo Perone wrote: > I do this by calling spamc over a courierfilter for a pre-scan, using a > systemwide bayes db and systemwide settings, rejecting anything over a > certain threshold, and then calling it again as xfilter over maildrop, > using user bayes and user settings. In this second run SA can change > anything it needs and, if recognized as spam, delivers it to a > $HOME/Maildir/.Spam maildir. That doesn't make the whole thing faster, > but it works very well and I'm very happy with the results.
However, this is exactly the type of inefficiency that the current design of Courier is trying to avoid. Pushing the same message through SpamAssassin twice is horrendously less efficient than saving a message to disk and then re-reading it when it comes to parsing its MIME structure would be. > Besides, at the courierfilter level you can't use user settings, at least > for messages with many recipients. Well, yes, you can. Obviously you just cannot (even just theoretically) modify the same message in several different ways. But subjecting it to different per-user accept/reject rules isn't a problem. Sam even once wrote a proposal for fine grained per-recipient acceptance/rejection: http://www.courier-mta.org/draft-varshavchik-exdata-smtpext.txt I see that the current version of Courier implements an "XEXDATA" SMTP extension. Sam, is that equivalent to the EXDATA proposal?
pgpe1v3zbub7o.pgp
Description: PGP signature
------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________ courier-users mailing list [email protected] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
