Abigail, thank you for your suggestions.
I upgraded to version 2.60 thinking that would help but I still do not see
BAYES_* scores in the xspam tag and logs. prior to october 9th the logs
showed lots of BAYES_60-99, and I don't know why it stoped. I am stuck I
have read the man files and googled, if you can help thank you in advance.
I run spamassasin through amavisd-new v. 20030616
A grep of my local.cf for bayes shows
use_bayes 1
#use_bayes 0
bayes_path /var/amavis/.spamassassin/bayes
bayes_auto_learn 1
bayes_auto_learn_threshold_nonspam 0.3
The only files I have in the .spamassassin directory are
auto-whitelist
auto-whitelist.db
bayes_seen
bayes_toks
user_prefs
$ sa-learn --dump magic # reports the following.
0.000 0 2 0 non-token data: bayes db
version
0.000 0 3583 0 non-token data: nspam
0.000 0 368 0 non-token data: nham
0.000 0 139100 0 non-token data: ntokens
0.000 0 1066246629 0 non-token data: oldest atime
0.000 0 1066339439 0 non-token data: newest atime
0.000 0 1066339712 0 non-token data: last journal
sync atime
0.000 0 1066287910 0 non-token data: last expiry
atime
0.000 0 0 0 non-token data: last expire
atime delta
0.000 0 0 0 non-token data: last expire
reduction count
spamassassin -D --lint prints the following dubug lines plus some other
stuff
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 '/usr/local/sbin', keeping.
debug: PATH included '/usr/local/bin', keeping.
debug: PATH included '/sbin', keeping.
debug: PATH included '/bin', keeping.
debug: PATH included '/usr/sbin', keeping.
debug: PATH included '/usr/bin', keeping.
debug: PATH included '/usr/X11R6/bin', keeping.
debug: PATH included '/root/bin', which doesn't exist, dropping.
debug: Final PATH set to:
/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/usr/X11R6/bin
debug: ignore: using a test message to lint rules
debug: using "/usr/share/spamassassin" for default rules dir
debug: using "/etc/mail/spamassassin" for site rules dir
debug: using "/root/.spamassassin" for user state dir
debug: using "/root/.spamassassin/user_prefs" for user prefs file
debug: bayes: 13398 tie-ing to DB file R/O
/var/amavis/.spamassassin/bayes_toks
debug: bayes: 13398 tie-ing to DB file R/O
/var/amavis/.spamassassin/bayes_seen
debug: bayes: found bayes db version 2
debug: Score set 3 chosen.
debug: Initialising learner
debug: dns_available set to yes in config file, skipping test
debug: is Net::DNS::Resolver available? yes
debug: all '*From' addrs: [EMAIL PROTECTED]
debug: running header regexp tests; score so far=0
debug: running body-text per-line regexp tests; score so far=2.077
debug: bayes corpus size: nspam = 3583, nham = 368
debug: uri tests: Done uriRE
debug: tokenize: header tokens for *F = "U*ignore
D*compiling.spamassassin.taint.org D*spamassassin.taint.org D*taint.org
D*org"
debug: tokenize: header tokens for *m = " 1066342148 lint_rules "
debug: bayes token 'N:H*m:NNNNNNNNNN' => 0.00484684684684685
debug: bayes token 'somewhat' => 0.0256190476190476
debug: bayes: score = 0.000852994703415655
debug: bayes: 13398 untie-ing
debug: bayes: 13398 untie-ing db_toks
debug: bayes: 13398 untie-ing db_seen
debug: Using results from Razor v2.36
debug: Found Razor2 part: part=0 engine=4 ct=0 cf=0
debug: leaving helper-app run mode
debug: Razor2 results: spam? 0 highest cf score: 0
debug: running raw-body-text per-line regexp tests; score so
far=2.077
debug: running uri tests; score so far=2.077
debug: uri tests: Done uriRE
debug: running full-text regexp tests; score so far=2.077
debug: Razor2 is available
debug: DCCifd is not available: no r/w dccifd socket found.
debug: Current PATH is:
/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/usr/X11R6/bin
debug: executable for dccproc was found at /usr/local/bin/dccproc
debug: DCC is available: /usr/local/bin/dccproc
debug: entering helper-app run mode
debug: DCC: got response: X-DCC-Servercave-Metrics:
INI-FILTER.interactivenw.com 1183; Body= 12772 Fuz1=590933
Fuz2=552319
debug: leaving helper-app run mode
debug: all '*To' addrs:
debug: RBL: success for 1 of 1 queries
debug: running meta tests; score so far=2.077
debug: is spam? score=-2.823 required=5
tests=BAYES_00,DATE_MISSING,NO_REAL_NAME
-----Original Message-----
From: Abigail Marshall [mailto:[EMAIL PROTECTED]
Sent: Thursday, October 16, 2003 2:49 PM
To: Matt Van Gordon; [EMAIL PROTECTED]
Subject: Re: [SAtalk] BAYES_* no longer appear in logs
Hello Matt,
Wednesday, October 15, 2003, 12:23:21 PM, you wrote:
MVG> Does the Bayesian filtering stop working if the
MVG> database becomes too lopsided?
It stops working if the database becomes corrupted, which
can happen in various ways. The first thing you should do is
look in your .spamassassin directory. You should have the
following files related to Bayes:
bayes_journal
bayes_msgcount
bayes_seen
bayes_toks
If you have any other files beginning with bayes_ but with
another extension (such as a lock file), that is a sign of
trouble.
I have tried various approaches to repairing that sort of
problem, but the only thing that really worked for me was to
delete all the bayes files and start over from scratch.
MVG> Is there a way to check how much ham and spam the
MVG> database has
Use this shell command:
spamassassin -D --lint
It will run a number of tests for Bayes, including a line
that tells you the ham/spam info. (on my server, this
currently reads:
debug: bayes corpus size: nspam = 7333, nham = 1281
If there is either insufficient spam or ham you will get a
specific error message telling you that.
Bayes periodically expires old tokens on its own; I am not
sure, but believe that it will NOT expire either ham or spam
if that leaves an insufficient corpus. While the accuracy
of the database might suffer if there is an imbalance, Bayes
should continue to run as long as it has the minimum
requisite of each.
MVG> and what can I do to insure that the
MVG> Bayesian filtering continues to function.
Just monitor it. I've had problems in the past myself, and
basically nothing seems to have really explained either the
source of my problem or how to fix it. I think the problem
is that it's possible (at least in versions 2.54/2.55) for
the salearn program to continue to run even after
encountering an error (such as lock file problem) and good
data can get overwritten with bad or incomplete data. I
don't think this is a frequent occurrence, but maybe it
happens from time to time with a heavy load of incoming mail
and more than one process trying to write to the database at
the same time. That's just a guess in any case, which comes
mostly from the fact that on my system I also seem to see
lock file issues at the same time I have encountered
problems or issues with the Bayes database. This in turn
could result from particular memory limitation issues on the
system -- I don't seem to have the problem any more since I
did a server upgrade that afforded more memory.
-Abigail
-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
SourceForge.net hosts over 70,000 Open Source Projects.
See the people who have HELPED US provide better services:
Click here: http://sourceforge.net/supporters.php
_______________________________________________
Spamassassin-talk mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
