On 4/5/21 3:46 PM, Todd Herr wrote:
Several jobs ago, when I was in position to set anti-spam policy for a mid-sized US-based cable ISP, if the RFC5321.From or RFC5322.From domain lacked both an MX record and an A/AAAA record, that was enough for me to reject the mail on the grounds that I was unwilling to accept anything to which the recipient could not reply.
I'm surprised at requiring an /MX/ record. I still see email routed to A / AAAA records for the domain when there isn't an MX record for said domain.
I wouldn't give your statement another thought if it was "an MX record or an A record or an AAAA record". But /requiring/ an /MX/ record is a toe stubber for me.
-- Grant. . . . unix || die
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ dmarc mailing list [email protected] https://www.ietf.org/mailman/listinfo/dmarc
