What are the issues with regard to a server being out of compliance with section 3.3.9 of RFC 1035? Is there a security issue, or some real-world issue other than the fact that RFC's clearly specify that the target of an MX record must be a name rather than an IP address?
If this is a BOFH issue, is there a patch for courier, or a switch somewhere that I might use to allow acceptance of non-compliant email? It doesn't appear that from a functional point of view it should matter that an MX record uses a number rather than a name, although I may not understand all the issues involved and don't know why the RFC is so specific in this regard. Any insight would be appreciated. I have a customer who is unhappy because one of his his correspondants can't reach him and the ISP with misconfigured DNS is both unresponsive and probably the only ISP available for many people in the community in which it's located. -- Lindsay Haisley | "Everything works | PGP public key FMP Computer Services | if you let it" | available at 512-259-1190 | (The Roadie) | <http://www.fmp.com/pubkeys> http://www.fmp.com | | ------------------------------------------------------- Sponsored by: ThinkGeek at http://www.ThinkGeek.com/ _______________________________________________ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
