On 11/04/2018 22:41, Carl Byington wrote:
So we could (do what they want) interpret mx:mail.example.com as if it
were a:mail.example.com - we won't be rejecting mail that the sending
domain intended for us to accept. But that just hides their error and
possibly increases the chances of yet more folks making the same
mistake.
What does your code do when it sees mx:mail.example.com, where there is
no mx record, but there is an a record?
Do what the RFC says.
From RFC 7208
"Note regarding implicit MXes: If the <target-name> has no MX record,
check_host() MUST NOT apply the implicit MX rules of [RFC5321
<https://tools.ietf.org/html/rfc5321>] by
querying for an A or AAAA record for the same name."
That's not ambiguous ;-)
_______________________________________________
mailop mailing list
mailop@mailop.org
https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
