Jeff Mincy wrote:
The question is: How does one fix the problem after it occurs?
The way to fix the problem is to relearn any incorrectly learned
messages. So any spam message that was incorrectly learned as ham,
either automatically or manually, needs to be correctly relearned as
spam using sa-learn. You should also learn as spam any spam messages
that hits BAYES_00, or anything less than BAYES_50. You should also
do the same thing for HAM messages hitting BAYES_50 - BAYES_99.
The more messages that you correctly train the more accurate and
definitive bayes will be.
If you don't have the incorrectly learned messages to retrain then you
can always start over by removing the bayes database files in your
.spamassassin directory.
Thank you for such a good, reasonable answer (it's good to see SOMEONE
is trying to answer questions with non-flippant responses). :-)
No, I don't still have the messages that were incorrectly trained.
So... it appears that wiping out the bayes database is the way to go.
One final question for this then: is there a "sa-learn" option I should
use for this, or is doing a simple "rm bayes*" in the .spamassassin
directory preferred?
--
Chris Barnes AOL IM: CNBarnes
chris-bar...@tamu.edu Yahoo IM: chrisnbarnes
Computer Systems Manager MSN IM: ch...@txbarnes.com
Department of Physics ph: 979-845-7801
Texas A&M University fax: 979-845-2590
