Thanks to everyone for the great discussions. Eventually with your help our trouble delivering to earthlink and some other email systems has been resolved (fingers crossed).
For our issue, the solution was found while reading an article about *ugh* exchange servers of all things. (recommended reading somewhere in this list a while ago) The author had our reject message perfectly : [<00>] XMail bounce: [EMAIL PROTECTED];Error=[550-EarthLink does not recognize your computer (209.121.70.9) as connecting from an EarthLink connection. If this is in error, please contact technical support. 550 relaying to <[EMAIL PROTECTED]> prohibited by administrator] He didn't discuss any errors that might be similar to our ErrCode = -162 ErrString = End of socket stream data errors, we we had those too. But I felt like those were just disconnects from servers my xmail server was trying to connect to in error, just as in the author's original conclusion about the nature of the earthlink message. He was trying to trouble shoot this from an exchange perspective which wasn't so helpful - but the conclusion he came to was a DNS problem. He writes that the DNS server in his MS SBS 2003 is intermittently faulty - and that having his SMTP server use his ISP's DNS resolved the issue. Then I thought about XMAIL and the choices we have. Without using [SmartDNSHost] I think I remember reading that XMAIL just asks the operating system to resolve DNS. Since none of our networks have any problems using Microsoft DNS, I just didn't think it was the DNS server that was failing. So - I started using SmartDNSHost and pointing to the DNS server on the machine on which XMAIL and the DNS server are running (instead of using SmartDNSHost to tell XMAIL to use my ISP's DNS server as recommended in the exchange article.) The Operating system itself, and the entire network it supports are all configured to use the SAME DNS server, and does so without problems. As soon as I began using SmartDNSHost, virtually ALL my lingering delivery problems have ceased. Gone, poof! Zap! So, the only thing that I changed was the way in which XMAIL reaches the dns server. I did NOT change the DNS server in any way. Without the SmartDNSHost entry, XMAIL asks the operating system to resolve (which in turn is configured to ask the SAME DNS server) , where when using SmartDNSHost XMAIL asks the DNS server directly. It would seem XMAIL gets different results from the same DNS server, depending upon how it reaches that server. I Hope this might help someone - heaven knows I was stuck on this and needed the group to help get it fixed. What do you think - are my conclusions faulty? What do you think the results mean? Edinilson I know it seems basic, but have you tried using SmartDNSHost? Maybe I missed that in one of the messages. But try pointing it to the same DNS server the OS is using (weird, I know) and see what happens. Tom Banting - your email was helpful also - have you resolved this issue for your networks yet? Thanks to everyone who contributed! Tony ----- Original Message ----- From: "Kroll, David" <[EMAIL PROTECTED]> To: <[email protected]> Sent: Saturday, March 12, 2005 9:09 PM Subject: [xmail] Re: Problems with hotmail.com > This is a Win2003 DNS issue. > Some mailservers behind firewalls which do not allow transfer of UDP > packets > larger than 512 bytes may not be able to return the MX record > > If your firewall restricts UDP packet transfers though, you may want to > verify that it will allow transfer of a MX record within the size > limitations specified by RFC1035: > > http://www.faqs.org/rfcs/rfc1035.html > > Windows 2003 server has included Extension Mechanisms for DNS (EDNS0) to > allow larger packets. If you run this command on a 2003 server: "dnscmd > Server Name/Config /EnableEDnsProbes 0", it fixes it without making any > changes to the firewall. > > -----Original Message----- > From: Tony Shiffer [mailto:[EMAIL PROTECTED] > Sent: Friday, March 11, 2005 4:39 PM > To: [email protected] > Subject: [xmail] Re: Problems with hotmail.com > > We have started to get these same errors - for the last 2-3 months. Never > any before then. It has happened sending to earthlink, hotmail, and some > others. Its does not allways seem to happen. Often, if the user resends > the message - it goes through just fine. > > It includes the error -162's , and some times error text that says that > relaying is prohibited, or that the sender is not recognized as being > connected to that ISPs network (which they aren't, of course). > > We have investigated DNS, RDNS, as well as the infastructure (NICs, > cabling, > > and even power supllies in the xmail server boxes.). Inone case, we even > had the ISP (level3.com) replace the network cable all the way from our > rack, back to the main switch. Nothing has made any difference. > > It happens on xmail 1.13 run on one old box, and xmail 1.20. - both > Windows > boxes. These boxes are in different locations on different subnets so > they > have nothing in common as far as ISP, hosting location, or domains being > handled by xmail. > > Tony > > > > ----- Original Message ----- > From: <[email protected]> > To: <[email protected]> > Sent: Friday, March 11, 2005 5:30 AM > Subject: [xmail] Re: Problems with hotmail.com > > >> Yes, issuing at DOS prompt: >> nslookup -type=MX hotmail.com 200.231.29.10 >> it is being resolved without problems. >> >> Below a SLOG from spool: >> >> >> [PeekTime] 1110537048 : Fri, 11 Mar 2005 07:30:48 -0300 >> << >> ErrCode = -162 >> ErrString = End of socket stream data >> SMAIL SMTP-Send MX = "mx1.hotmail.com." SMTP = "mailserver" From = >> "[EMAIL PROTECTED]" To = "[EMAIL PROTECTED]" Failed ! Snip - To unsubscribe from this list: send the line "unsubscribe xmail" in the body of a message to [EMAIL PROTECTED] For general help: send the line "help" in the body of a message to [EMAIL PROTECTED]
