Those can be ignored. They are by design.
--
Kevin A. McGrail
Member, Apache Software Foundation
Chair Emeritus Apache SpamAssassin Project
https://www.linkedin.com/in/kmcgrail - 703.798.0171
On Thu, Nov 19, 2020 at 9:26 AM Dean Carpenter <
deano-spamassas...@areyes.com> wrote:
> On 2020-11-18
On 2020-11-18 1:45 pm, RW wrote:
> On Wed, 18 Nov 2020 09:44:21 -0500
> Dean Carpenter wrote:
> 0.0 NO_DNS_FOR_FROM DNS: ENVELOPE SENDER HAS NO MX OR A DNS RECORDS -0.5
> FROM_IS_REPLY_TO From and REPPLY-TO is the same 0.0 SPF_NONE SPF: SENDER DOES
> NOT PUBLISH AN SPF RECORD
> Heh, the
On Wed, 18 Nov 2020 09:44:21 -0500
Dean Carpenter wrote:
>
> > 0.0 NO_DNS_FOR_FROM DNS: ENVELOPE SENDER HAS NO MX OR A DNS RECORDS
> > -0.5 FROM_IS_REPLY_TO From and REPPLY-TO is the same
> > 0.0 SPF_NONE SPF: SENDER DOES NOT PUBLISH AN SPF RECORD
> Heh, the FROM_IS_REPLY_TO description has a
On 18 Nov 2020, at 9:44, Dean Carpenter wrote:
Greetings -
I'm finalizing my ansible playbook for building up a nice mail system
with all the goodies, with spamassassin being very central to it all.
I
have a test server set up in Azure that I run tests with using swaks
(great tool). I push
Greetings -
I'm finalizing my ansible playbook for building up a nice mail system
with all the goodies, with spamassassin being very central to it all. I
have a test server set up in Azure that I run tests with using swaks
(great tool). I push both ham and spam to it, with and without the old
