RE: configure question

2015-01-18 Thread Marieke Janssen
>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

Mail::SpamAssassin::Plugin::Check::_head_tests_0_1, skipping: Jan 17 08:00:12.091 [2891] warn: (Insecure dependency in require while running with -T switch at (eval 1037) line 9

2015-01-18 Thread mls
Hi, I am seeing more and more emails that cause the following PERL warnings when scanned with spamassassin Jan 17 08:00:12.091 [2891] warn: rules: failed to compile Mail::SpamAssassin::Plugin::Check::_head_tests_0_1, skipping: Jan 17 08:00:12.091 [2891] warn: (Insecure dependency in require wh

Re: Mail::SpamAssassin::Plugin::Check::_head_tests_0_1, skipping: Jan 17 08:00:12.091 [2891] warn: (Insecure dependency in require while running with -T switch at (eval 1037) line 9

2015-01-18 Thread Kevin A. McGrail
On 1/18/2015 7:18 AM, mls wrote: I am seeing more and more emails that cause the following PERL warnings when scanned with spamassassin Based on a quick search, this page leads me to believe it's fixed in a newer version of SA: https://bugzilla.redhat.com/show_bug.cgi?id=1141695 Regards, KAM

Re: configure question

2015-01-18 Thread Michael Williamson
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

Re: configure question

2015-01-18 Thread RW
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

Re: configure question

2015-01-18 Thread Michael Williamson
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=

Re: configure question

2015-01-18 Thread John Hardin
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

Re: configure question

2015-01-18 Thread Michael Williamson
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