On 2/20/2014 5:56 PM, Bob Proulx wrote:
With the sa-update channel problems now behind us I have upgraded
again to 3.4.0 and am using it. It appears now that using -D turns
off Bayes?
spamassassin -d -t -D < mail.file | less
No BAYES_* anything is recorded. Versus using:
spamassassin -d -t < mail.file | less
Where BAYES_* scoring is seen. Neither is it enabled even when
debugging "bayes" specifically. Making that feature rather hard to
use now. :-(
spamassassin -d -t -D bayes < mail.file | less
It looks to me that -D now disables Bayes as a regression in 3.4.0.
Thanks,
Bob
Can't recreate and can't see how that's possible. -D turns on debug
output and I don't see any references to the config option in the Bayes
library. Not saying you are wrong but it sounds a bit unlikely.
And here's a dummy devel system with bayes turned on with no tokens:
spamassassin -d -t -D < /tmp/1.mbox 2>&1 | grep -i bayes
Feb 20 18:00:55.153 [19142] dbg: plugin: loading
Mail::SpamAssassin::Plugin::Bayes from @INC
Feb 20 18:00:55.437 [19142] dbg: config: fixed relative path:
/var/lib/spamassassin/3.004000/updates_spamassassin_org/23_bayes.cf
Feb 20 18:00:55.437 [19142] dbg: config: using
"/var/lib/spamassassin/3.004000/updates_spamassassin_org/23_bayes.cf"
for included file
Feb 20 18:00:55.437 [19142] dbg: config: read file
/var/lib/spamassassin/3.004000/updates_spamassassin_org/23_bayes.cf
Feb 20 18:00:56.872 [19142] dbg: plugin:
Mail::SpamAssassin::Plugin::Bayes=HASH(0x901ca5c) implements
'learner_new', priority 0
Feb 20 18:00:56.873 [19142] dbg: bayes: learner_new
self=Mail::SpamAssassin::Plugin::Bayes=HASH(0x901ca5c),
bayes_store_module=Mail::SpamAssassin::BayesStore::DBM
Feb 20 18:00:56.889 [19142] dbg: bayes: learner_new: got
store=Mail::SpamAssassin::BayesStore::DBM=HASH(0x9286940)
Feb 20 18:00:56.889 [19142] dbg: plugin:
Mail::SpamAssassin::Plugin::Bayes=HASH(0x901ca5c) implements
'learner_is_scan_available', priority 0
Feb 20 18:00:56.890 [19142] dbg: bayes: tie-ing to DB file R/O
/root/.spamassassin/bayes_toks
Feb 20 18:00:56.891 [19142] dbg: bayes: tie-ing to DB file R/O
/root/.spamassassin/bayes_seen
Feb 20 18:00:56.891 [19142] dbg: bayes: found bayes db version 3
Feb 20 18:00:56.892 [19142] dbg: bayes: DB journal sync: last sync: 0
Feb 20 18:00:56.892 [19142] dbg: bayes: not available for scanning, only
3 spam(s) in bayes DB < 200
Feb 20 18:00:56.892 [19142] dbg: bayes: untie-ing
Feb 20 18:00:56.900 [19142] dbg: bayes: tie-ing to DB file R/O
/root/.spamassassin/bayes_toks
Feb 20 18:00:56.900 [19142] dbg: bayes: tie-ing to DB file R/O
/root/.spamassassin/bayes_seen
Feb 20 18:00:56.900 [19142] dbg: bayes: found bayes db version 3
Feb 20 18:00:56.901 [19142] dbg: bayes: DB journal sync: last sync: 0
Feb 20 18:00:56.901 [19142] dbg: bayes: not available for scanning, only
3 spam(s) in bayes DB < 200
Feb 20 18:00:56.901 [19142] dbg: bayes: untie-ing
Feb 20 18:01:08.109 [19142] info: rules: meta test LOC_SHORT has
dependency 'BAYES_00' with a zero score
What does spamassassin -d -t -D < mail.file 2>&1 | grep -i bayes show
for you?
Regards,
KAM
