>> I am using bayes, but it didn't catch it. I was quite surprised at >> that. > > Doesn't look to me like you are using bayes. There is no bayes score in > the headers. > Oh. I thought I was. I do get reports in some messages. Here's the debug from this particular message: [12541] dbg: config: read file /home/peloruso/.spamassassin/23_bayes.cf [12541] dbg: config: read file /home/peloruso/.spamassassin/70_sare_bayes_poison_nxm.cf [12541] dbg: plugin: loading Mail::SpamAssassin::Plugin::Bayes from @INC [12541] dbg: config: fixed relative path: /home/peloruso/.spamassassin/updates_spamassassin_org/23_bayes.cf [12541] dbg: config: using "/home/peloruso/.spamassassin/updates_spamassassin_org/23_bayes.cf" for included file [12541] dbg: config: read file /home/peloruso/.spamassassin/updates_spamassassin_org/23_bayes.cf [12541] dbg: config: fixed relative path: /home/peloruso/etc/mail/spamassassin/skip/updates_spamassassin_org/23_bayes.cf [12541] dbg: config: using "/home/peloruso/etc/mail/spamassassin/skip/updates_spamassassin_org/23_bayes.cf" for included file [12541] dbg: bayes: tie-ing to DB file R/O /home/peloruso/.spamassassin/skip/bayes/bayes_toks [12541] dbg: bayes: tie-ing to DB file R/O /home/peloruso/.spamassassin/skip/bayes/bayes_seen [12541] dbg: bayes: found bayes db version 3 [12541] dbg: bayes: DB journal sync: last sync: 1221706869 [12541] dbg: bayes: DB journal sync: last sync: 1221706869 [12541] dbg: bayes: corpus size: nspam = 4748, nham = 1680 [12541] dbg: bayes: score = 2.02454774056449e-08 [12541] dbg: bayes: DB expiry: tokens in DB: 136363, Expiry max size: 150000, Oldest atime: 1216674739, Newest atime: 1221711862, Last expire: 1220940612, Current time: 1221712855 [12541] dbg: bayes: DB journal sync: last sync: 1221706869 [12541] dbg: bayes: untie-ing
Anything look funny in there? I see a very low score: 2.02e-08, but isn't it still working?
