Hi,
X-Spam-Status and related headers indicate a spamassassin instance
processing (and classifying) your emails, rather than using bogofilter.
Was spamassassin installed recently? Can you try to uninstall it?
Regards.
On 30/07/2014 08:51, Stephen Davies wrote:
Today, amavisd on my mail server changed the way it processes spam.
Before today, spam headers in clean emails looked like:
X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.2.4
X-Virus-Scanned: amavisd-new at sdc.com.au
because I have configured it to use bogofilter as it's spam filter.
Emails detected as spam by bogofilter were quarantined and never hit an
inbox.
Today, the headers have changed to:
X-Virus-Scanned: amavisd-new at sdc.com.au
for clean emails and
X-Virus-Scanned: amavisd-new at sdc.com.au
X-Spam-Flag: YES
X-Spam-Score: 3.354
X-Spam-Level: ***
X-Spam-Status: Yes, score=3.354 tagged_above=0 required=3
tests=[ALL_TRUSTED=-1, HTML_MESSAGE=0.001,
HTML_TAG_BALANCE_BODY=0.712, LOTS_OF_MONEY=0.001,
MIME_HEADER_CTYPE_ONLY=1.996, MIME_HTML_ONLY=1.105,
MISSING_HEADERS=1.207, RP_MATCHES_RCVD=-0.668]
autolearn=no autolearn_force=no
for what it thinks is spam (but isn't).
I have not touched the amavisd configuration since February last year
and amavisd has not been updated since last month.
What else can have changed?
Cheers and thanks,
Stephen
--
Danti Gionatan
Supporto Tecnico
Assyoma S.r.l. - www.assyoma.it
email: [email protected] - [email protected]
GPG public key ID: FF5F32A8
