From: Matt Kettler [mailto:[EMAIL PROTECTED]
Sent: Mon 25/08/2003 17:01
To: Christie, Stuart; [EMAIL PROTECTED]
Subject: Re: [SAtalk] Spamassassin Bayesian and Razor problems
I'll answer the bayes half of your question.
It appears
you are running ./check_bayes_db as root.. however, root's bayes
database is
by default located in /root/.spamassassin/bayes_*.
Amavsid is running as
the user amavisd, which does not have the same home
directory as root, so the
bayes databases are expected to be
in
/var/amavisd/.spamassassin/bayes_*.
Hence the problem.. you're
training emails into roots bayes database, which
is not the same one used for
amavisd.
One way around this is to force the bayes_path to be the same
for all users
in your local.cf.
Another way is to use root's
user_prefs to force only root's bayes_path to
be
/var/amavisd/.spamassassin/bayes_. This way root trains the same bayesdb
as
amavis, but other local accounts still have separate databases in their
home
directory (useful for testing if nothing else).
At 02:49 PM
8/25/2003 +0100, Christie, Stuart wrote:
>I'm having some problems with
Spamassassin 2.55 (using spamd) and both
>it's Bayesian and Razor2
components. Firstly, I'm getting the following
>error in the spamassassin
debugging - "debug: bayes: no dbs present,
>cannot scan:
/var/amavisd/.spamassassin/bayes_toks". I've been able to
>teach the
database, as shown below, but spamd is still having the same
>problem
scanning the file.
>
>#
./check_bayes_db
>0.000
0
0 0 non-token data: db format =
on-the-fly
>probs, expiry,
scan-counting
>0.000
0 278
0 non-token data:
nspam
>0.000
0
1 0 non-token data:
nham
>0.000 0
30640 0 non-token data:
ntokens
>0.000
0
0 0 non-token data: oldest
age
>0.000
0 5842 0
non-token data: current
scan-count
>0.000
0
0 0 non-token data: last expiry
scan-count
>
>The permissions on the bayes_* files are set such that
the "spamd" user
>can read/write, and I've made sure the DB_File Perl
module is installe
---------------------------------------------------------------------------------------------
This e-mail was checked and validated by the dns email content management service.
For information on how to improve your organisations email management contact [EMAIL PROTECTED]
---------------------------------------------------------------------------------------------
