On 2 Apr 2019, at 09:49, @lbutlr <krem...@kreme.com> wrote:
> Ah, yes, Good point.
Maybe it will work now, I rand the message from two days ago through spamc and
got:
X-Spam-Status: No, score=-94.6 required=5.0 tests=BAYES_99,BAYES_999,
DKIM_ADSP_ALL,DKIM_INVALID,DKIM_SIGNED,MIME_HEADER_CTYPE_ONLY,
RCVD_IN_DNSWL_NONE,USER_IN_WHITELIST autolearn=no autolearn_force=no
version=3.4.2
X-Spam-Report:
* -100 USER_IN_WHITELIST From: address is in the user's white-list
* 0.2 BAYES_999 BODY: Bayes spam probability is 99.9 to 100%
* [score: 0.9999]
* 3.5 BAYES_99 BODY: Bayes spam probability is 99 to 100%
* [score: 0.9999]
* -0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at
* https://www.dnswl.org/, no trust
* [54.240.13.1 listed in list.dnswl.org]
* 0.8 DKIM_ADSP_ALL No valid author signature, domain signs all mail
* 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily
* valid
* 0.1 DKIM_INVALID DKIM or DK signature exists, but is not valid
* 0.7 MIME_HEADER_CTYPE_ONLY 'Content-Type' found without required
* MIME headers
So there it has picked up the whitelist. I will await the next delivery
notification and see what happens.
I did update several packages on my freeBSD install.
Could this be an issue in how SpamAssassin-milter and spamassasin interact?
like the filter not picking up the local.cf file?
--
Over 3,500 gay marriages and, what, no hellfire? I was promise hellfire.
And riots. What gives? -- Mark Morford
