Re: [AMaViS-user] Fwd: Re: SpamAssassin Plugins

[Mike C. <lis...@ca...>]

On 8/29/09 9:57 PM, Jeff Grossman wrote:
> On 8/29/2009 8:17 PM, Mike Cappella wrote:
>>   On 8/29/09 10:34 AM, Jeff Grossman wrote:
>>>   How do I figure out where/how spamassassin is loading modules?
>>>   According to my amavis logwatch report the following plugins are being
>>>   loaded.  But, I know for a fact that the AWL plugin is disabled in the
>>>   v310.pre file in /etc/spamassassin.  This is on a Debian testing
>>>   system.  I did a grep of AWL in the /etc/spamassassin directory and the
>>>   only item that came up was the commented out line.  I then did a grep of
>>>   AWL in the /etc/amavis/conf.d directory and it came up empty.
>>>
>>>
>>
>>   FYI:  It all comes from this amavis log line (ymmv):
>>
>>   Aug 29 16:02:20 glacier amavis[14742]: SpamAssassin loaded plugins:
>>   AWL, AutoLearnThreshold, Bayes, BodyEval, Check, DCC, DKIM, DNSEval,
>>   HTMLEval, HTTPSMismatch, Hashcash, HeaderEval, ImageInfo, MIMEEval,
>>   MIMEHeader, Pyzor, Razor2, RelayEval, ReplaceTags, SPF, SpamCop,
>>   URIDNSBL, URIDetail, URIEval,
>
> The problem is that line doesn't tell you how the module was loaded.  In
> my case it was a .pre file located in /usr/share/spamassassin that was
> causing my problems.  During my initial troubleshooting I was only
> looking in /etc/spamassassin and /etc/amavis/conf.d which is where I
> thought all configuration files were located.

Understood; it was just an FYI clarifying where the data comes from, and 
that amavis-logwatch is only reporting what it is reads.

And amavis doesn't likely know in which file the directive resides.  You 
can use a command such as this:

# use sudo or su, as per your preference
# change the -u user to suit your config

$ sudo -H -u amavis spamassassin -t -Dall some-test-file  2>&1 | egrep 
'AWL|config: read file'

to give you a list of .cf files to grep, and verify the loading of AWL 
(or any plugin for that matter).

--
Mike