----- Original Message ----- > From: "Matt Kettler" <[EMAIL PROTECTED]> > To: "Juliano Simões" <[EMAIL PROTECTED]>; <users@spamassassin.apache.org> > Sent: Monday, November 01, 2004 12:58 PM > Subject: Re: Bayes sometimes not used >
> At 06:38 PM 10/31/2004, Juliano Simões wrote: > >See below sample outputs from subsequent executions of > >"/usr/bin/spamassassin -tLD < spam_msg_file": > > since you're using -D for debug output, is there anything in the debug that > might give some clues? > > Do both use the same score set? Yes. > Any complaints about lock failures? No, locks and unlocks look good. > Did either trigger autolearning? Nope. > Did either trigger a bayes sync (can cause a dramatic change in the bayes > DB as the journal is integrated)? Yes, it seems like they did. Please, take a look at the following debug log scenarios from SA testing the same message: ** 1. Have bayes hits ** ... debug: bayes: opportunistic call found expiry due debug: Syncing Bayes and expiring old tokens... debug: lock: 32684 created /home/spamd/.spamassassin/bayes.mutex debug: lock: 32684 trying to get lock on /home/spamd/.spamassassin/bayes with 10 timeout debug: lock: 32684 link to /home/spamd/.spamassassin/bayes.mutex: link ok debug: bayes: 32684 tie-ing to DB file R/W /home/spamd/.spamassassin/bayes_toks debug: bayes: 32684 tie-ing to DB file R/W /home/spamd/.spamassassin/bayes_seen debug: bayes: found bayes db version 3 debug: refresh: 32684 refresh /home/spamd/.spamassassin/bayes.mutex debug: Syncing complete. debug: bayes: 32684 untie-ing debug: bayes: 32684 untie-ing db_toks debug: bayes: 32684 untie-ing db_seen debug: bayes: files locked, now unlocking lock ** 2. No bayes hits ** ... debug: bayes: opportunistic call found journal sync due debug: Syncing Bayes and expiring old tokens... debug: lock: 4276 created /home/spamd/.spamassassin/bayes.mutex debug: lock: 4276 trying to get lock on /home/spamd/.spamassassin/bayes with 10 timeout debug: lock: 4276 link to /home/spamd/.spamassassin/bayes.mutex: link ok debug: bayes: 4276 tie-ing to DB file R/W /home/spamd/.spamassassin/bayes_toks debug: bayes: 4276 tie-ing to DB file R/W /home/spamd/.spamassassin/bayes_seen debug: bayes: found bayes db version 3 debug: refresh: 4276 refresh /home/spamd/.spamassassin/bayes.mutex debug: Syncing complete. debug: bayes: Not available for scanning, only 0 spam(s) in Bayes DB < 200 debug: bayes: not scoring message, returning undef debug: bayes: 4276 untie-ing debug: bayes: 4276 untie-ing db_toks debug: bayes: 4276 untie-ing db_seen debug: bayes: files locked, now unlocking lock So, if bayes sync is the problem, why is this happen so often? I run "sa-learn --sync" many times per day, after training ham and spam. Is there a way to prevent spamassassin from triggering a sync every time? Regards, Juliano Simões Gerente de Tecnologia Axios Tecnologia e Serviços http://www.axios.com.br [EMAIL PROTECTED] +55 41 324-1993
