So did we ever get a straight answer on why IMail doesn't even try to use the 2ndry MX record? I couldn't find it.
Yes, here is a re-cap:
o IMail will follow the RFCs 100% of the time (except with some old versions)
o IMail will treat a TCP RST as a temporary failure, not a permanent failure.
As is often the case, there were a few other unrelated "Me too"'s in the thread (such as the one where the secondary MX record pointed to a lame mailserver, which rejects E-mail with "No such user", which is a problem on the remote end). But this seems to sum it up. There is no evidence that the latest versions of IMail do not follow the RFCs, but the "TCP RST" is not covered by the RFCs (although some other mailservers treat it as a permanent failure, in which case the secondary would be tried).
-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/
