We are trying to accomplish something called "Successful E-mail Delivery' and "Happy Customers".
It's a great theory, but when they are sending mail to "bozo admins" that have no clue what they are doing (the admin that intentionally has a primary MX record that keeps responding with a 421), you can't please everyone.
Think of it this way: What if IMail had a bug in it that caused it to look up the A record for the "mail" host on a domain if no MX record were present. So if "example.com" has no MX record, instead of checking the A record and then giving up (as the RFCs specify, and all mailservers do), this hypothetical version of IMail would also try "mail.example.com". Some bozo admin has the mail.example.com host set up, but no MX record and no A record for example.com. Now, IMail can deliver E-mail to this broken domain, but no other mailservers can't. You're saying that all other mailservers should be required to start working in this non-RFC-specified behavior, just because IMail does, and there is someone set up incorrectly?
Although it's easy to blame IMail, it's really the admin whose broken domain your customers are trying to send to that is the one who is causing the problems.
-Scott
---
Declude JunkMail: The advanced anti-spam solution for IMail mailservers.
Declude Virus: Catches both viruses and vulnerabilities in E-mail, with no annual licensing fees.
--- [This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)]
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/
