> The better MTAs detect the too-common broken "MX ip.ad.re.ss" record > and interpret the intent of the error and try to deliver the IP, > rather than not deliver the mail at all, while logging an "invalid > MX record".
To my mind, this particular "forgiving" policy simply encourages less-than-attentive sysadmins. You can bet that plenty of other errors, particularly other DNS errors, will come along with this blatant misconfiguration, and my conscience won't let me work around it -- I'm much less likely to work around this, for example, than to allow incoming connections without PTRs and suchlike. Certainly, I don't even see any reason to log an "error" if the MTA best-guesses/normalizes the RR and delivers anyway; who ever takes action on that error? Anyway, there are always sysadmin-specific (and site-specific) rules regarding whether a policy encourages the "education" of partners/clients vs. just making our end look bad. This is one policy that I always enforce as part of the "education" category, while I know that you enforce others that I don't. . . an interesting divergence. --Sandy ------------------------------------ Sanford Whiteman, Chief Technologist Broadleaf Systems, a division of Cypress Integrated Systems, Inc. e-mail: [EMAIL PROTECTED] To Unsubscribe: http://www.ipswitch.com/support/mailing-lists.html List Archive: http://www.mail-archive.com/imail_forum%40list.ipswitch.com/ Knowledge Base/FAQ: http://www.ipswitch.com/support/IMail/
