On 8/2/19 7:19 AM, Matus UHLAR - fantomas wrote:
X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on
myserver.mydomain.com
X-Spam-Level: **
X-Spam-Status: No, score=2.3 required=4.0
tests=BAYES_99,BAYES_999,DKIM_SIGNED,
DKIM_VALID,DKIM_VALID_AU,DKIM_VERIFIED,HTML_FONT_LOW_CONTRAST,
HTML_MESSAGE,KAM_SHORT,URIBL_BLACK autolearn=no autolearn_force=no
version=3.4.2
I missed this last time: This is not an amavis header. You apparently run
spamassassin on different lace.
amavis header looks like this:
X-Spam-Status: No, score=1.173 required=6.31 tests=[ALL_TRUSTED=-1,
BAYES_00=-1.9, DCC_CHECK=1.1, DIGEST_MULTIPLE=0.293,
DOS_OUTLOOK_TO_MX=2.845, FSL_BULK_SIG=0.84,
FSL_HELO_NON_FQDN_1=0.001,
HELO_NO_DOMAIN=0.001, HTML_MESSAGE=0.001, MIME_HTML_MOSTLY=0.1,
PYZOR_CHECK=1.392, SUBJ_ALL_CAPS=0.5, TRUSTED_SUBMISSION=-3]
autolearn=no autolearn_force=no
Yes, thank you Matus, you are not alone, I missed this:
This server is in a cluster that was rebuilt after several severe storms
recently here and apparently Spamassassin remnant configs remained in
the Postfix master.cf after the rebuild massaging.
They were calling spamd separately, I removed those calls and the logs
and headers appear more correct now:
example:
X-Spam-Status: No, score=0 required=4 tests=[BAYES_00=-1.9,
HTML_MESSAGE=0.001, MISSING_MIMEOLE=1.899, RCVD_IN_DNSWL_NONE=-0.0001]
autolearn=no autolearn_force=no
