That's what I don't understand. I talked to the "Admin" over at neo.tamu.edu and he said they haven't had any complaints about e-mail not getting to them.
So obviously, no matter what I here from anyone else, my own personal experience and basic reasoning skills makes me believe, yes, what Scott is saying is probably true, it makes sense, but IMail should be doing something different. Someone should own up to that, somewhere. I would like a log file of IMail actually switching to a secondary MX record, that would be nice to see. Anybody? Bralynn ----- Original Message ----- From: "Rick Leske" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, April 02, 2003 9:06 PM Subject: Re: [IMail Forum] So ya say IMail handles Secondary MX records correct do ya? > Hey.. this is good info.. > > Does anyone have a work around 'hack' or what ever to force IMail to try any > other avail MX records "regardless" what the 4.x.x/5.x.x response is? How > about a future 'check box' or something to allow this. Many mail servers > are broke, setup wrong, or what ever that have caused us a lot of grief > too - but doesn't cause other email servers any sending problems like > hotmail.com, yahoo.com, msn.com, aol.com, etc etc etc.... > > ~Rick > > ----- Original Message ----- > From: "R. Scott Perry" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> > Sent: Wednesday, April 02, 2003 7:46 PM > Subject: Re: [IMail Forum] So ya say IMail handles Secondary MX records > correct do ya? > > > > > So ya say IMail handles Secondary MX records correct do ya? > > > > <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!). > > ___________________________________________________________________ > Virus Scanned and Filtered by http://www.FamHost.com E-Mail System. > > > 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/ > > [Scanned by AwesomeNet Anti-Virus] > > [Scanned by AwesomeNet Anti-Virus] 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/
