http://issues.apache.org/SpamAssassin/show_bug.cgi?id=5497
------- Additional Comments From [EMAIL PROTECTED] 2007-06-06 19:11 ------- > Should I set bayes_auto_learn_threshold_nonspam "back" to 0.1, > remove the sa-update config files, disable my regular sa-updating, > destroy my current bayes database and start over? I don't think that the auto_learn_threshold should ever be blindly set to an arbitrary number. I might even argue that we should not try to provide a default value for the autolearn threshold. You can look over a large sample of ham and spam to see what makes sense as thresholds at your site. Without having to carefully verify every mail you probably can come up with a pretty good number for a score below which you can be pretty certain that you hardly ever see spam and another number for a score above which you never see ham. Then use those numbers. If the bug here is that an auto_learn_ham threshold of -1 makes no sense, then the fix is to chabge the threshold to something that makes sense for your installation, not elimnate sa_update. On the other hand, if this problem appears after an sa-update, I really would like to see what you can learn about the affect of the sa-updateed rules by looking at the output of spamassassin -t as I mentioned in comment #11. There could be something not quite right about some updated rule even if the overall problem can be characterised as a bad auto_learn_ham threshold. ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
