Bayes doesn't seem to be working for me!

There's a number of possible reasons this may be happening.

debug: bayes: Not available for scanning, DB_File not installed

This is a default, conservative setting; SA's Bayes is often used in an administration-free mode, and we determined experimentally that lower thresholds require more 'babysitting'.

However, if you're happy to keep an eye on things, go ahead and reduce these numbers by using the 'bayes_min_ham_num' and 'bayes_min_spam_num' settings in your configuration file. Numbers as low as 10 will work fine, as long as you expect the odd mistake during the first few messages, and will run sa-learn to correct their classification. (This is called 'mistake-based training'.)

This can be checked by running "spamassassin -D --lint" and keeping an eye out for this line:

debug: bayes: Not available for scanning, only 0 spam(s) in 
Bayes DB < 200

Still No Bayes Filtering? Watch out for the "rebuild" option!

If you find that SA never seems to learn messages, try using sa-learn --dump magic to find out more about your database. The line "nham" is the number of ham messages SA has learned, and the line "nspam" is the number of spam messages SA has learned.

There's a subtle gotcha in the options. The command sa-learn --no-rebuild --spam spam_directory works. However, the command sa-learn --rebuild --spam spam_directory will not work; it will rebuild but not learn!

To defer rebuilding until after all the messages have been learned, use:

sa-learn --ham --no-rebuild ham_directory
sa-learn --spam --no-rebuild spam_directory
sa-learn --rebuild


BayesNotWorking (last edited 2010-08-20 01:06:08 by KenyonRalph)