Matthias Andree wrote: > Take this with a grain of salt, I'm biased (being the bogofilter > co-maintainer): > > IMHO the SpamAssassin Bayes stuff should be disabled -- for various reasons: > > 1. is that it causes a major performance issue, even on lightly loaded > Pentium D and Xeon 2.8 equipped servers, which causes filtering to be > aborted through amavis's timeouts (at least for my older amavisd-new > version). > > 2. SA's self-registering stuff should be disabled - Bayes filters need > to know what the human that is to receive the messages considers > spam, not what a machine second-guesses. > > 3. centralistic Bayes filtering doesn't work well, > as you've just seen in one of the failure modes that are sort of > expected for this class of filters > > 4. per-user databases don't scale too well > > 5. Bayes requires users to be permanently alert and correct mistakes. > > I'm not saying that SpamAssassin alone or Bayes are bad, but > SpamAssassin's Bayes implementation is, and integrating it with > amavisd-new doesn't ameliorate the pain. > > 3 to 5 are generic issues that affect all trainable/Bayesian filters.
Thanks. I knew most of this, which is why I wasn't going to bother trying to train databases this time around. But what do you mean by "self-registering" ? -- Jo Rhett Network/Software Engineer Net Consonance ------------------------------------------------------------------------- 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 _______________________________________________ AMaViS-user mailing list AMaViS-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amavis-user AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3 AMaViS-HowTos:http://www.amavis.org/howto/
