On 30.12.2006, at 19:46, Bernd Wurst wrote: > Additionally, I would like to do something like this (simplified): > call spamc: > * if score > 10, reject it > * if score > 4 and < 10, add an appropriate header field to the > message
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. Besides, at the courierfilter level you can't use user settings, at least for messages with many recipients. I also use dotcourier functionality for other things, such as "catchall" addresses for individual subdomains - never had problems using both dotcourier and maildrop. Sometimes I also wish courierfilter was as flexible and "event" oriented as I saw it happen with sendmail/milter, but then again, courier is very modular so if that is an important issue you can use sendmail. I'm happy with courier esmtp module right now. Regards, Lorenzo ------------------------------------------------------------------------- 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
