Bayes Problem
Daniel Gercke
gercke at HNM.DE
Thu Mar 18 11:06:06 GMT 2004
every night i do a cronjab
/usr/bin/sa-learn --rebuild -p /etc/MailScanner/spam.assassin.prefs.conf
--debug-level --force-expire
I become this:
debug: Score set 0 chosen.
debug: running in taint mode? yes
debug: Running in taint mode, removing unsafe env vars, and resetting PATH
debug: PATH included '/sbin', keeping.
debug: PATH included '/bin', keeping.
debug: PATH included '/usr/sbin', keeping.
debug: PATH included '/usr/bin', keeping.
debug: Final PATH set to: /sbin:/bin:/usr/sbin:/usr/bin
debug: using "/usr/share/spamassassin" for default rules dir
debug: using "/etc/mail/spamassassin" for site rules dir
debug: mkdir //.spamassassin failed: mkdir //.spamassassin: Permission
denied at /usr/lib/perl5/site_perl/5.8.0/Mail/SpamAssassin.pm line 1279
--> why it will try //.spamassassin ? Where can i define only to try in
"/var/spool/spamassassin/"
debug: using "/etc/MailScanner/spam.assassin.prefs.conf" for user prefs file
debug: bayes: 31762 tie-ing to DB file R/O
/var/spool/spamassassin/bayes_toks
debug: bayes: 31762 tie-ing to DB file R/O
/var/spool/spamassassin/bayes_seen
debug: bayes: found bayes db version 2
debug: Score set 2 chosen.
debug: Initialising learner
debug: Initialising learner
debug: Syncing Bayes journal and expiring old tokens...
debug: lock: 31762 created
/var/spool/spamassassin/bayes.lock.ftp2.hnm.de.31762
debug: lock: 31762 trying to get lock on /var/spool/spamassassin/bayes
with 0 retries
debug: lock: 31762 link to /var/spool/spamassassin/bayes.lock: link ok
debug: bayes: 31762 tie-ing to DB file R/W
/var/spool/spamassassin/bayes_toks
debug: bayes: 31762 tie-ing to DB file R/W
/var/spool/spamassassin/bayes_seen
debug: bayes: found bayes db version 2
debug: bayes: expiry check keep size, 75% of max: 112500
debug: bayes: token count: 211145, final goal reduction size: 98645
debug: bayes: First pass? Current: 1079605804, Last: 1079605438, atime:
0, count: 0, newdelta: 0, ratio: 0
debug: bayes: Can't use estimation method for expiry, something fishy,
calculating optimal atime delta (first pass)
--> what is it? how can i solve these problem?
debug: bayes: atime token reduction
debug: bayes: ======== ===============
debug: bayes: 43200 210413
debug: bayes: 86400 210413
debug: bayes: 172800 193563
debug: bayes: 345600 171021
debug: bayes: 691200 134201
debug: bayes: 1382400 112262
debug: bayes: 2764800 112018
debug: bayes: 5529600 111932
debug: bayes: 11059200 111914
debug: bayes: 22118400 111831
debug: bayes: couldn't find a good delta atime, need more token
difference, skipping expire.
--> why? how can i solve these problem?
debug: Syncing complete.
debug: bayes: 31762 untie-ing
debug: bayes: 31762 untie-ing db_toks
debug: bayes: 31762 untie-ing db_seen
debug: bayes: files locked, now unlocking lock
debug: unlock: 31762 unlink /var/spool/spamassassin/bayes.lock
Should i use bayes rebulid option in mailscanner.conf? What is a good time?
What means bayes_auto_expire = 0 in spam.assassin.conf should it be
uncommentet?
Thanks
--
Daniel Gercke
programmierung . system managements
--
[Diese Nachricht ist frei von Viren und gefaehrlichen Dateianhaengen.
Schutz vor Viren und Spam von haus neuer medien. Bei Fragen oder Interesse Kontakt ueber mailscanner at hnm.de oder 03834 83130.]
More information about the MailScanner
mailing list