<sigh>
Once again, yes.
***************************************
03:30 00:19 SMTP-(00000E3C) Trying neo.tamu.edu (0)
03:30 00:19 SMTP-(00000E3C) Connect neo.tamu.edu [128.194.103.210:25] (1)
03:30 00:19 SMTP-(00000E3C) 421 SMTP service not available, closing transmission channel
***************************************
After 30 tries, gives the user: Delivery failed 30 attempts: [EMAIL PROTECTED]
Great! That's *exactly* what IMail should do. The 421 response means "Please try me again soon, I will be back up shortly."
A NSLOOKUP recovers:
That doesn't matter. :)
What I can't figure out is why would IMail not start to use the secondary MX after a while? I searched the entire log, it never tried the MX 100.
That's because it is supposed to keep re-trying the primary mailserver.
I understand the real problem is with their MX setup, but shouldn't IMail try the 2nd mail server? I thought it only wouldn't try the secondary if it received the wrong acknowledgment, as if it were being rebooted, etc.
Again, IMail will properly go to the secondary MX record *when it should*. If the primary is not reachable, for example. But if the primary is reachable and says "Come on back!", IMail will.
The 421 response is usually used when the server is rebooting (don't ask me how a server can respond to SMTP queries while it is rebooting, though!).
-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/
