Hi All Has anyone else come across this one? I have outbound messages queued up for domains where there primary server is down. These queue up and are not delivered which would seem fair enough on the face of it. Just one problem the destination system has multiple MX records and the other hosts are up. Why does Exchange refuse to use them? Even if I force the connection they do not leave? Eventually they go of their own accord but this takes several minutes or even hours? I cannot say at this stage if this is as a result of the primary server coming back on line. I suspect it is. > server 126.96.36.199 Default Server: ns1.lon.ipmh.telecity.net Address: 188.8.131.52 > set q=mx > mtsn.org.uk Server: ns1.lon.ipmh.telecity.net Address: 184.108.40.206 Non-authoritative answer: mtsn.org.uk MX preference = 10, mail exchanger = scanmailext.easymail.va.ifl net mtsn.org.uk MX preference = 20, mail exchanger = mx1.easymail.va.ifl.net mtsn.org.uk MX preference = 30, mail exchanger = mx2.easymail.va.ifl.net mtsn.org.uk nameserver = dns2.rmplc.co.uk mtsn.org.uk nameserver = dns0.rmplc.co.uk mtsn.org.uk nameserver = dns1.rmplc.co.uk scanmailext.easymail.va.ifl.net internet address = 220.127.116.11 mx1.easymail.va.ifl.net internet address = 18.104.22.168 mx2.easymail.va.ifl.net internet address = 22.214.171.124 > I can telnet the second server just fine. The first one drops the connection almost immediately. I suspect that is the answer? I am guessing that since it does make a connection of sorts, albeit very briefly, it never tries the second record as it thinks it is connected and thus never checks the other MX records. Above and below are relevant screen shots. 421 SMTP service not available, closing transmission channel Connection to host lost. Can someone tell me if I am correct and if there is any way around this please. I know that strictly speaking, if my theory is correct, it could be classed as a firewall issue at the remote end but that doesn't help me deliver mail. The only short term way I see around this is to set up an extra Virtual SMTP server and restrict the address space to just that domain and forward to the second record host explicitly rather than using DNS. Although that won't help with the trapped messages I suspect? Any ideas, comments or suggestions please? Many thanks in advance, Regards, Paul Lemonidis.