Re: bayes not available ?

journal sync: last sync: 0 [20058] dbg: bayes: not available for scanning, only 0 ham(s) in bayes DB < 200 [20058] dbg: bayes: untie-ing [20058] dbg: bayes: untie-ing db_toks [20058] dbg: bayes: untie-ing db_seen It's a new server and in my local.conf: bayes_auto_learn

bayes not available ?

: 0 [20058] dbg: bayes: not available for scanning, only 0 ham(s) in bayes DB < 200 [20058] dbg: bayes: untie-ing [20058] dbg: bayes: untie-ing db_toks [20058] dbg: bayes: untie-ing db_seen It's a new server and in my local.conf: bayes_auto_learn

Re: bayes: not available for scanning

--lint [5284] dbg: bayes: not available for scanning, only 0 spam(s) in bayes DB < 200 [5284] dbg: bayes: corpus size: nspam = 124095, nham = 262008 [5284] dbg: bayes: DB expiry: tokens in DB: 119251, Expiry max size: 15, Oldest atime: 1144827345, Newest atime: 1146270059, Last exp

Re: sa-learn killed, bayes not available

: bayes: found bayes db version 3 debug: bayes: Not available for scanning, only 0 spam(s) in Bayes DB < 200 rescanning doesn't do any good, because sa-learn still knows about the messages it's already looked at. I have to start training all over by deleting bayes_seen and bayes

Re: sa-learn killed, bayes not available

debug: bayes: found bayes db version 3 debug: bayes corpus size: nspam = 592, nham = 562 After a killed process: debug: bayes: found bayes db version 3 debug: bayes: Not available for scanning, only 0 spam(s) in Bayes DB < 200 rescanning doesn't do any good, because sa-learn still kn

sa-learn killed, bayes not available

ore a killed process: debug: bayes: found bayes db version 3 debug: bayes corpus size: nspam = 592, nham = 562 After a killed process: debug: bayes: found bayes db version 3 debug: bayes: Not available for scanning, only 0 spam(s) in Bayes DB < 200 rescanning doesn't do any good, bec

bayes: not available for scanning

Hi all,Running SA 3.1.0. I have been using the Bayes DB for 8-9 months now. All of a sudden it seems like a lot of Spam is getting through, and training it with the new Spam does not seem to have any effect. There is a quirk in the following output: >spamassassin -D --lint[5284] dbg: bayes:

Re: Bayes not Available

Andy Jezierski wrote: You need to teach Bayes at least 200 spam and 200 non-spam messages before it will do anything for you. Thanks. Is it true that SA will ignore DCC and Razor (evethough they are enabled) if I turn on training mode? Regards, Norman Zhang

Re: Bayes not Available

Norman Zhang <[EMAIL PROTECTED]> wrote on 03/14/2005 03:29:25 PM: > debug: bayes: Not available for scanning, only 0 spam(s) in Bayes DB < 200 You need to teach Bayes at least 200 spam and 200 non-spam messages before it will do anything for you. Andy

Re: Bayes not Available

g something? Regards, Norman Zhang debug: bayes: found bayes db version 3 debug: bayes: Not available for scanning, only 0 spam(s) in Bayes DB < 200 debug: bayes: 9566 untie-ing debug: bayes: 9566 untie-ing db_toks debug: bayes: 9566 untie-ing db_seen

RE: Bayes not Available

Norman Zhang wrote: > Hi, > > When I run amavisd debug-sa, I see the following. Is my SA bayes > misconfigured? May I ask for a few pointers? > bayes_path /var/lib/amavis/var/.spamassassin Should be /var/lib/amavis/var/.spamassassin/bayes surely (the final "/bayes" is not a path but rather a fil

Bayes not Available

Hi, When I run amavisd debug-sa, I see the following. Is my SA bayes misconfigured? May I ask for a few pointers? Regards, Norman Zhang debug: bayes: Not available for scanning, only 0 spam(s) in Bayes DB < 200 required_hits 5 rewrite_header Subject [SPAM] report_safe 0 skip_rbl_check