You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@spamassassin.apache.org by realshock <wa...@gmail.com> on 2009/04/09 05:38:45 UTC
use_auto_whitelist error in lint
Hello
on lint test i get the following message:
-------------------
[root@mailgw ~]# spamassassin --lint
[2871] warn: config: failed to parse line, skipping: use_auto_whitelist 0
[2871] warn: lint: 1 issues detected, please rerun with debug enabled for
more information
-------------------
i commented out "use_auto_whitelist 0" line from
/etc/MailScanner/spam.assassin.prefs.conf and i disabled "loadplugin
Mail::SpamAssassin::Plugin::AWL" in
/etc/mail/spamassassin/RulesDuJour/v310.pre
and didn't find that plugin in init.pre
i'm running spamassassin 3.1.8 and MailScanner 4.58.9
Any ideas how to fix this?
--
View this message in context: http://www.nabble.com/use_auto_whitelist-error-in-lint-tp22963928p22963928.html
Sent from the SpamAssassin - Users mailing list archive at Nabble.com.
Re: use_auto_whitelist error in lint
Posted by realshock <wa...@gmail.com>.
Jeff Mincy-2 wrote:
>
>
>
> spamassassin -D --lint prints out the config files, eg:
> spamassassin -D --lint 2>&1 | fgrep 'config: read file'
>
> The use_auto_whitelist is in one of those config files.
> -jeff
>
>
Worked ... spamassassin --lint returning no errors > Rules update are back
to normal
Thank you much for both :-)
--
View this message in context: http://www.nabble.com/use_auto_whitelist-error-in-lint-tp22963928p22972364.html
Sent from the SpamAssassin - Users mailing list archive at Nabble.com.
Re: use_auto_whitelist error in lint
Posted by Jeff Mincy <je...@delphioutpost.com>.
From: realshock <wa...@gmail.com>
Date: Thu, 9 Apr 2009 06:56:05 -0700 (PDT)
Matt Kettler-3 wrote:
> Find out where else you've got "use_auto_whitelist 0" in your config,
> and remove it.
> On the plus side, it does confirm you've correctly disabled the plugin.
I searched all over the place, and following your directions, do you think
this command will find where it is?
# grep -iR use_auto_whitelist /*
spamassassin -D --lint prints out the config files, eg:
spamassassin -D --lint 2>&1 | fgrep 'config: read file'
The use_auto_whitelist is in one of those config files.
-jeff
Re: use_auto_whitelist error in lint
Posted by realshock <wa...@gmail.com>.
Matt Kettler-3 wrote:
>
>
> Find out where else you've got "use_auto_whitelist 0" in your config,
> and remove it.
> On the plus side, it does confirm you've correctly disabled the plugin.
>
>
I searched all over the place, and following your directions, do you think
this command will find where it is?
# grep -iR use_auto_whitelist /*
--
View this message in context: http://www.nabble.com/use_auto_whitelist-error-in-lint-tp22963928p22971450.html
Sent from the SpamAssassin - Users mailing list archive at Nabble.com.
Re: use_auto_whitelist error in lint
Posted by Matt Kettler <mk...@verizon.net>.
realshock wrote:
> Hello
> on lint test i get the following message:
> -------------------
> [root@mailgw ~]# spamassassin --lint
> [2871] warn: config: failed to parse line, skipping: use_auto_whitelist 0
> [2871] warn: lint: 1 issues detected, please rerun with debug enabled for
> more information
> -------------------
> i commented out "use_auto_whitelist 0" line from
> /etc/MailScanner/spam.assassin.prefs.conf and i disabled "loadplugin
> Mail::SpamAssassin::Plugin::AWL" in
> /etc/mail/spamassassin/RulesDuJour/v310.pre
> and didn't find that plugin in init.pre
>
> i'm running spamassassin 3.1.8 and MailScanner 4.58.9
>
> Any ideas how to fix this?
>
>
Find out where else you've got "use_auto_whitelist 0" in your config,
and remove it. You found it in spam.assassin.prefs.conf, but it must be
somewhere else as well. This might just be root's user_prefs, which
wouldn't affect MailScanner runs, but does affect lint runs as root.
Since you've disabled the loadplugin, the "use_auto_whitelist" config
option is no longer supported, and its presence somewhere is what's
generating the lint warning.
On the plus side, it does confirm you've correctly disabled the plugin.