On 10-06-15 17:25, Ben wrote:
> I have a curious conundrum.
>
> A piece of spam received shows the following in the header when
> processed via amavis and spamd :
> DATE_IN_PAST_03_06,
> HTML_MESSAGE,
> RCVD_IN_BL_SPAMCOP_NET,
> RCVD_IN_MSPIKE_H4,
> RCVD_IN_MSPIKE_WL,
> RDNS_DYNAMIC,
> SHORTENED_URL_SRC
>
> But when the exact piece of Spam is fed directly into spamassassin (i.e
> spamassassin < spam.txt), I get a different series of tests :
>
> HTML_MESSAGE,
> MY_CUSTOM2_SPAM,
> RCVD_IN_BL_SPAMCOP_NET,
> RCVD_IN_BRBL_LASTEXT,
> RCVD_IN_MSPIKE_H4,
> RCVD_IN_MSPIKE_WL,
> RDNS_DYNAMIC,
> SHORTENED_URL_SRC
>
>
> The difference being that my custom spam test ("MY_CUSTOM2_SPAM") is not
> run via amavis, but is run directly.
amavisd uses the spamassassin libraries internally, it does not use the
spamassassin command, nor spamd. If you update parts of the config,
you'll need to reload/restart amavisd.
> My spam test is configured in /etc/spamassassin/local.cf, and I have run
> "su - debian-spamd -c "spamassassin --lint" && service spamassassin
> reload". I have even tried sa-compile just incase my local.cf changes
> needed to be compiled before they are recognised.
>
> spamd does share the same config files as the spamassassin binary, right ?
>
> This is on Ubuntu 14.04LTS, SpamAssassin version 3.4.0 running on Perl
> version 5.18.2, amavisd 1:2.7.1-2ubuntu3.
>
