Dave Walker <davewal...@ubuntu.com> writes: > Micah Anderson wrote: >> I got a phish message that was understood by bayes as: >> >> -2.6 BAYES_00 BODY: Bayesian spam probability is 0 to 1% >> [score: 0.0000] >> >> So I traiend with spamc -L spam but even after that I am still getting >> BAYES_00. Shouldn't the training have bumped that score up? >> >> Thanks for any info, >> > In order for Bayes to actually make a difference, it needs plenty of > training. It's disabled by default in most installs - unless you have > at least 200 of both spam and ham taught. This needs to be done > manually, unless you have autolearn enabled.
Yeah, I've been running this bayes db for a couple years now, so I am sure I've passed the 200 mark :) I'm wondering if my bayes DB is too poisoned now and maybe needs to be reset? > To see what is really going on run "$ spamassassin -D < > /path/to/the/email > /dev/null", and see if you can learn anything as to > why it's not working as expected. Indeed, when I do this, I find these bayes related log entries: [13244] dbg: bayes: corpus size: nspam = 6798614, nham = 19136735 [13244] dbg: bayes: tok_get_all: token count: 175 [13244] dbg: bayes: score = 0 > Also, to see how experienced your Bayes knowledge is - use "$ sa-leanrn > --dump magic" This shows me that I have no idea what these magic things are :) Does this tell you anything useful? 0.000 0 3 0 non-token data: bayes db version 0.000 0 6798614 0 non-token data: nspam 0.000 0 19136753 0 non-token data: nham 0.000 0 1063157695 0 non-token data: ntokens 0.000 0 1241301616 0 non-token data: oldest atime 0.000 0 1241416889 0 non-token data: newest atime 0.000 0 0 0 non-token data: last journal sync atime 0.000 0 1241344830 0 non-token data: last expiry atime 0.000 0 43200 0 non-token data: last expire atime delta 0.000 0 496607 0 non-token data: last expire reduction count micah
