I think you are right.
Running spamassassin manually appears to use the user's "user_prefs"
configuration file, and bayes database. I need to get amavisd to do it
that way too, if possible.
On 1/18/15, John Hardin wrote:
> On Sun, 18 Jan 2015, Michael Williamson wrote:
>
>> Here is an example of
On Sun, 18 Jan 2015, Michael Williamson wrote:
Here is an example of the automatically inserted spam headers:
Return-Path:
X-Spam-Status:
tests=[BAYES_00=-1.9
And here, I ran the same email through spamassassin manually from the
command line:
X-Spam-Report:
* 3.5 BAYES_99
OK, thanks. I will read the amavisd FAQ.
However, I am skeptical about your explanation for the spam score difference.
Here is an example of the automatically inserted spam headers:
Return-Path:
...
X-Spam-Flag: NO
X-Spam-Score: -1.106
X-Spam-Level:
X-Spam-Status: No, score=-1.106 tagged_above=
On Sun, 18 Jan 2015 09:06:00 -0700
Michael Williamson wrote:
> Yes, amavisd is running and modifying the file
> "/etc/amavisd/amavisd.conf" has an effect on the spamassassin header
> messages added to emails. Thanks, that answers that question.
Amavisd uses SA as a library, you don't need to be r
Yes, amavisd is running and modifying the file
"/etc/amavisd/amavisd.conf" has an effect on the spamassassin header
messages added to emails. Thanks, that answers that question.
Now, the next question is, if I manually run
# spamassassin -t < spam_filename
I get a different, much higher spam sc
>Spamassassin seems not to be getting the configuration changes that I make.
Is it possible you run something like Amavis that controls SpamAssassin?
Headers and spamscore are usual controlled there and will override local.cf.
/MJ
OK. Here it is:
#!/bin/sh
#
# spamassassin This script starts and stops the spamd daemon
#
# chkconfig: - 78 30
# processname: spamd
# description: spamd is a daemon process which uses SpamAssassin to check \
# email messages for SPAM. It is normally called by spamc \
#
--As of January 17, 2015 4:20:36 PM -0700, Michael Williamson is alleged to
have said:
to both /etc/mail/spamassassin/local.cf and
/home//.spamassassin/user_prefs,
I check the file permissions to be readable by all. I restart it
# service spamassassin restart
--As for the rest, it is mine.
