James Bucanek wrote:
Greetings, As you can see, the Bayes filter has nailed it as spam, but it still only gets a score of 3.6.
Bayes scores are really quite low in SA v3 - 3.0.2. You may want to upgrade to 3.0.3 to get the newer Bayes scores, or revert to the v2.6x scores in your local.cf. We've done the later here with no ill effect, by putting the following block in our local.cf.
score BAYES_00 0 0 -1.665 -2.599 score BAYES_05 0 0 -0.925 -0.413 score BAYES_20 0 0 -0.730 -1.951 score BAYES_40 0 0 -0.276 -1.096 score BAYES_50 0 0 1.567 0.001 score BAYES_60 0 0 3.515 1.372 score BAYES_80 0 0 3.608 2.087 score BAYES_95 0 0 3.514 3.063 score BAYES_99 0 0 4.070 4.886
I currently have my threshold set to 7.0. I've been considering lowering it again (maybe to 5.0), but am paranoid about false positives. I can go through my mailbox and see ham that has scores of 3 or even 4.
I only tag my personal/family accounts, so FP's, while annoying, are only a folder away (I tag at 4, everyone else at 5). However, I've only had 2 FP in the last year, and both were from mortgage companies when I was going through a refi. Would you mind posting some of your higher-scoring ham, with headers? It's possible you have a misconfiguration in some of your settings.
I was previously using a client-side Bayes filtering system and was getting 99.8+% spam identification rates. SA has been, so far, a bit of a disappointment and I'm sure it's my fault. :)
My home account probably gets a 5 9's identification rate, with a near zero FP rate. SARE rulesets, network tests, and a well trained Bayes database make a huge difference in the performance of SA. Make sure your trusted_networks are set correct and enable network tests, URIBL tests, and Razor/Pyzor. Check out the CustomRuleset section of the wiki for info on SARE and other rulesets.
- S
