> >From today's log: > >02:25 00:09 SMTP-(000005D0) Trying domainname.com (0) >02:25 00:10 SMTP-(000005D0) MX connect fail "xxx.xxx.xxx.xxx"
>Could you supply the domain name? That would help a lot, and prevent >mistakes in figuring out what is happening. > > -Scott No need, I got it. The MX connect fail provided the clue. I went down the path of "Well, it sees the correct address, so it isn't DNS. Why else could it not connect....?" If it's not a protocol issue, then I need to look at the other two possibilities, the transport layer, and the physical layer. The physical layer was easy, the cables were plugged in and the server was responding on all IPs. That left the transport layer. Meaning that for whatever reason, the server could not see the target. I could ping the target, so that didn't seem probable. Time to read up on how IMAIL connects. It turns out that IMAIL uses the IP address of the default mail host to establish its outbound connections. In my case, I bound that host to an address different from our hosted clients. On Sunday a change was made on one of our firewalls that prevented un-authorized IPs from going out. Anyone want to take a guess as to whether that IP was listed as authorized? So, at that point, IMAIL was attempting to make connections out, but the firewall was not letting it. A pretty close match was found at: http://support.ipswitch.com/kb/IM-19981110-DD02.htm I added that IP to the list, went to get a soda, and my server shoved a days worth of mail out in about 10 minutes. Go figure. What a waste of a day. But all is well now. Thanks to everyone for the help. rusty 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/
