paul, Monday, October 28, 2002 you wrote: P> Ok Eric, we did that, but ALWAYS had our primary and b/u listed P> with no problems, this problem started Saturday AM <12:02 by the P> first mx error> after removing the secondary Friday, this started P> the following day. Coincidence? conspiracy theories abound!
When I have this happen the first thing I test is whether or not I can telnet to any of the IP addresses tried by IMAIL from my IMAIL server. I have yet to find a single case where I could connect manually so I think IMAIL is reporting exactly what it should. It may be some sort of IMAIL problem but I have yet to see anything that persuades me. Next I try to connect from another machine on my same network and if that fails then I try a tracert to try and determine where the failure occurs. Next I try to connect from a point outside my network - usually my workstation. If I can connect from outside my network but not from inside my network then I can determine whether or not I want to initiate a ticket to my provider. Usually I don't because the problem is usually some a router table that is messed up and will be fixed within a few hours whether I escalate or not. Trying to get two ISPs to fix something at a router level at a handoff node is almost futile. These kinds of things fortunately are uncommon but certainly they do occur, at least in my experience. Terry Fritts 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/
