Hi

I didnt have that option but I did have bayes_sql_username set

I have added the sql_override as well.

I have restarted and will see what happens.

I am using the ubuntu exim-daemon heavy and it calls spamd directly.

Ben

Axb <mailto:axb.li...@gmail.com>
09 September 2015 15:10via Postbox <https://www.postbox-inc.com/?utm_source=email&utm_medium=sumlink&utm_campaign=reach>


No idea how Exim interfaces to SA but...

Do you have
bayes_sql_override_username
in local.cf ?
if no, try adding that and restart spamd

h2h
Ben Whyall <mailto:b...@whyall-systems.co.uk>
09 September 2015 15:03via Postbox <https://www.postbox-inc.com/?utm_source=email&utm_medium=sumlink&utm_campaign=reach>
Hi

I have a mail setup serving multiple domains that is running on ubuntu lts 14.04.03 lts.

Spamassassin 3.4.0
Perl 5.18.2
Exim 4.82

We have bayes stored in a mysql database

When spamassassin is run from exim, it is always returning a hit on rule Bayes_00 with a score of 0.0000, however if you run spamassassin < message, it will return a different bayes score.

in the /etc/defaults/spamassassin file we have the following

OPTIONS="-p 987 -s /var/log/spamd.log --nouser-config --helper-home-dir -H -u spamd"

the output of sa-learn -u spamd --dump magic is

0.000 0          3          0  non-token data: bayes db version
0.000          0      13794          0  non-token data: nspam
0.000          0       5619          0  non-token data: nham
0.000          0    1157620          0  non-token data: ntokens
0.000          0 1398925984          0  non-token data: oldest atime
0.000          0 1441801878          0  non-token data: newest atime
0.000 0 0 0 non-token data: last journal sync atime
0.000          0 1441797057          0  non-token data: last expiry atime
0.000 0 5529600 0 non-token data: last expire atime delta 0.000 0 783449 0 non-token data: last expire reduction count

Could anyone suggest how I might find out what is going awry ?

Ben


--
Sent from Postbox <https://www.postbox-inc.com/?utm_source=email&utm_medium=siglink&utm_campaign=reach>

Reply via email to