Eric, This is definitely the case.
In my own experience I have seem a good many cases where IMAIL re-queued the message upon connecting to the primary but never receiving any response at all. When I would check these occurrences I would see in my logs where the primary mx server was checked but never an occurrence where the secondary was checked. When I would telnet to the primary I would get a very long pause between connect and message. So I believe that where there is a very long delay in the response from the primary that IMAIL gives up and does not check the secondary. The only solution to this problem I've found is to force an entry to the hosts file. It may be designed behavior but it surely seems wrong and it definitely makes one have to intervene a lot. Terry Fritts Monday, July 15, 2002 you wrote: ES> IMail _will_ use the 2nd MX only if there is no response from the first. ES> Response is considered any kind of connection to port 25 on the receiving ES> end. so, if you telnet to port 25 of the foreign server and get anything ES> other than a 5xx or no connect then IMail will properly not go any further ES> in its delivery process. Please visit http://www.ipswitch.com/support/mailing-lists.html to be removed from this list. An Archive of this list is available at: http://www.mail-archive.com/imail_forum%40list.ipswitch.com/ Please visit the Knowledge Base for answers to frequently asked questions: http://www.ipswitch.com/support/IMail/
