Re: [AMaViS-user] SpamAssassin Plugins

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

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.
>
>        SpamAssassin plugins
>            Loaded
>                AWL
>                AutoLearnThreshold
>                Bayes
>                BodyEval
>                Check
>                DKIM
>                DNSEval
>                HTMLEval
>                HTTPSMismatch
>                Hashcash
>                HeaderEval
>                ImageInfo
>                MIMEEval
>                MIMEHeader
>                Pyzor
>                Razor2
>                RelayCountry
>                RelayEval
>                ReplaceTags
>                SPF
>                SpamCop
>                URIDNSBL
>                URIDetail
>                URIEval
>                VBounce
>                WLBLEval
>                WhiteListSubject
>                iXhash
>
>
> Thanks for any help you can offer me.

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,