Lucio Crusca writes:
Hello *,courier-0.65 here (Debian). For a particular domain, courier refuses todeliver messages because it violates RFC 1035. Correct, it actually does and I added it to esmtproutes for the time being. However the same domain has two MXrecords configured. One violates RFC since it's in the form domain.com MX 20 mx.host.ip.address. but the other one is in the form domain.com MX 20 mail.domain.com. mail.domain.com IN A mx.host.ip.address. Now, while I understand the first one is wrong, I wonder why courier couldn't just ignore it, and use the RFC 1035 compliant mx record instead.
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.
pgpGGfM229gws.pgp
Description: PGP signature
------------------------------------------------------------------------------ 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 courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
