<html>
<head>
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-2">
</head>
<body text="#000000" bgcolor="#FFFFFF">
On 8/2/19 7:19 AM, Matus UHLAR - fantomas wrote:<br>
<br>
<blockquote type="cite" cite="mid:20190802121953.GB9053@fantomas.sk">
<blockquote type="cite">X-Spam-Checker-Version: SpamAssassin 3.4.2
(2018-09-13) on <br>
myserver.mydomain.com <br>
X-Spam-Level: ** <br>
X-Spam-Status: No, score=2.3 required=4.0
tests=BAYES_99,BAYES_999,DKIM_SIGNED, <br>
DKIM_VALID,DKIM_VALID_AU,DKIM_VERIFIED,HTML_FONT_LOW_CONTRAST, <br>
HTML_MESSAGE,KAM_SHORT,URIBL_BLACK autolearn=no
autolearn_force=no <br>
version=3.4.2 <br>
</blockquote>
<br>
I missed this last time: This is not an amavis header. You
apparently run <br>
spamassassin on different lace. <br>
amavis header looks like this: <br>
<br>
X-Spam-Status: No, score=1.173 required=6.31
tests=[ALL_TRUSTED=-1, <br>
BAYES_00=-1.9, DCC_CHECK=1.1, DIGEST_MULTIPLE=0.293, <br>
DOS_OUTLOOK_TO_MX=2.845, FSL_BULK_SIG=0.84,
FSL_HELO_NON_FQDN_1=0.001, <br>
HELO_NO_DOMAIN=0.001, HTML_MESSAGE=0.001,
MIME_HTML_MOSTLY=0.1, <br>
PYZOR_CHECK=1.392, SUBJ_ALL_CAPS=0.5,
TRUSTED_SUBMISSION=-3] <br>
autolearn=no autolearn_force=no <br>
<br>
</blockquote>
Yes, thank you Matus, you are not alone, I missed this:<br>
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.<br>
They were calling spamd separately, I removed those calls and the
logs and headers appear more correct now: <br>
example:<br>
<pre>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
</pre>
</body>
</html>