Payal Rathod <[EMAIL PROTECTED]> wrote on 10/04/2004 12:34:58 PM:
> On Mon, Oct 04, 2004 at 01:13:50PM -0400, Theo Van Dinter wrote:
> > Watch the rest of the debug output, run "spamassassin -D", etc.
>
> You mean spamd -D, right. spamassassin -D just waits for till I
> press ctrl-c
>
> I modified the local.cf file slightly to have,
> #bayes_path /root/.spamassassin/bayes
> use_bayes 1
>
> # spamd -D > sss 2>&1
> # grep -i bayes sss
> # grep -i bayes sss
> debug: bayes: 4983 tie-ing to DB file R/O /root/.spamassassin/bayes_toks
> debug: bayes: 4983 tie-ing to DB file R/O /root/.spamassassin/bayes_seen
> debug: bayes: found bayes db version 2
> debug: bayes corpus size: nspam = 267, nham = 235
> debug: bayes token 'N:H*m:NNNNNNNNNN' => 0.998514469453376
> debug: bayes token 'H*F:D*org' => 0.978
> debug: bayes token 'somewhat' => 0.958
> debug: bayes: score = 0.999904058950849
> debug: bayes: 4983 untie-ing
> debug: bayes: 4983 untie-ing db_toks
> debug: bayes: 4983 untie-ing db_seen
> debug: is spam? score=7.477 required=4.5
tests=BAYES_99,DATE_MISSING,NO_REAL_NAM
>
> Does this mean that bayes is working?
>
> With warm regards,
> -Payal
Yep, bayes is working, notice the BAYESS_99 rule hit above. Another thing
to keep in mind is that Bayes only kicks in after you have 200 ham & 200
spam messages learned. Looks like your bayes has only recently gone above
the 200 mark.
Andy
