On Tue, Jun 26, 2012 at 12:52 PM, Sam Varshavchik <[email protected]>wrote:
>
> There are no prescribed means for handling bad DNS data. If DNS is wrong,
> one cannot have any expectation that it will work in any particular way,
> even if some parts of it are correct.
>
That's not quite correct, there are prescribed means for handling bad DNS
data in the context of Internet mail delivery.
RFC 2821 specifies how to handle MX RRs:
http://tools.ietf.org/html/rfc2821#section-5
RFC 5321 clarifies:
http://tools.ietf.org/html/rfc5321#section-5
To put it briefly: it would appear that the RFC authors think that the good
old "be tolerant in what you accept" principle still applies, and it would
not be unreasonable for an MTA to skip a broken MX record and try the other
record(s), if any.
However, it would perhaps not be unreasonable to say "bah, screw you guys,
I'm going home" either.
--
Jan
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
courier-users mailing list
[email protected]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
