bayes engine not working?

[Steve Freegard]

Anjana,

The correct way of calling check_bayes_db is:  './check_bayes_db
--dbpath=/var/spool/spamassassin/bayes', not the way you have described
below which doesn't seem to give an error if you get the path wrong it just
seems to use the default of ~/.spamassassin as the path which is probably
why you are seeing this.

You might also try doing: 'sa-learn -D -p
/etc/MailScanner/spam.assassin.prefs.conf --rebuild 2>&1 | less' and see
what output you get from that.

Hope this helps.

Kind regards,
Steve

--
Steve Freegard
Systems Manager
Littlehampton Book Services Ltd.


-----Original Message-----
From: Patel, Anjana [mailto:Anjana.Patel at CRANFIELD.AC.UK]
Sent: 29 May 2003 13:38
To: MAILSCANNER at JISCMAIL.AC.UK

Hello,

I've upgraded spamassassin to v2.55 and added the bayes_path to the
spam.assassin.prefs.conf as per the FAQ.  The bayes_* files are being
updated which is the good news but worryingly check_bayes_db -db
/var/spool/spamassassin/bayes only reports 1 spam message which is the
test message I sent to sa-learn.  I've noticed that several spam
messages in the log have BAYES_ rules so is there a problem or is this
normal in the beginning?  We use Outlook so I'm not sure how to feed
sa-learn with the current spam in my inbox.

0.000        0        0        0  non-token data: db format = on-the-fly
probs, expir
y, scan-counting
0.000        0        1        0  non-token data: nspam
0.000        0        9        0  non-token data: nham
0.000        0     1522        0  non-token data: ntokens
0.000        0        0        0  non-token data: oldest age
0.000        0       13        0  non-token data: current scan-count
0.000        0        0        0  non-token data: last expiry scan-count

thanks
Anjana

--
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the sender and delete the message from your mailbox.

This footnote also confirms that this email message has been swept by
MailScanner (www.mailscanner.info) for the presence of computer viruses.