Lindsay Haisley wrote: > > Gordon, here's a suggested patch for the spamassassin.py filter for > pythonfilter. This is perhaps just a demonstration of concept since you > would probably want to streamline the code.
I don't see anything obvious that needs to be cleaned up in your patch. I will probably apply the it (except for the init message -- none of the other filters print their configuration, and I'm weird about consistency), but the benefit of the configuration item is probably fairly small. Adding the SA headers in the filter doesn't prevent you from running SA again during local delivery and doesn't change the score you'll get from doing so. The only advantage you get is a very small performance benefit from not re-writing messages that are small enough to be scanned. Compared to the actual scanning, saving the results of the scan should be very fast, and a small fraction of the overall process. Beyond that, I'd caution you that you'll have to change the way some things work in order for user preferences to be reliable in combination with global filtering. You'll need to aggregate all of your users' whitelists (but not blacklists) in the daemon user's settings in order to make sure that users receive mail when they whitelist an address, even if the score exceeds your global limit. ------------------------------------------------------------------------------ _______________________________________________ courier-users mailing list [email protected] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
