On 07.01.2007, at 21:57, Julian Mehnle wrote: > 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.
I agree, but I don't see an alternative to have this kind of setup, where mail over a certain threshold is rejected (resulting in a notification of the user in case it's a false positive, yet without generating backscatter) and the rest of the spam delivered, modified, to a user-spam maildir. > Well, yes, you can. Obviously you just cannot (even just > theoretically) > modify the same message in several different ways. If I understood correctly the rest of this thread, at the moment it is not a good idea to modify the message even once, within a courierfilter. So it wouldn't be possible to save a modified copy, which is desired in my as well as in other setups. > But subjecting it to > different per-user accept/reject rules isn't a problem. The only, quite ugly alternative I see here: checking the message for each recipient within the courierfilter, rejecting it above a certain threshold, and below it, saving the checked, modified message copies in a temporary directory, storing it's ID in a database (for example), and then using a script in maildrop to "recover" that modified message upon delivery. But I think such a solution would really be torturing Sam's work even more ;o It certainly would be more interesting in the future to be able to notify courier about changes, so that he can reparse it. That said, I am very happy with the whole product and with the feedback on this mailing list (even if it is, sometimes, a bit harsh: but I learned old and new things, so thanx for all of it :)) > http://www.courier-mta.org/draft-varshavchik-exdata-smtpext.txt I see. Sounds straightforward, yet the question is how widely has this been implemented. 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
