Francis, this also true for me: > Yes > The problem is EXACTLY 'XMAIL comes back to the A record for obscure > reasons (internal or due to bad dns responses ?) even if MX records > exists for the target domains'.
I'm glad there *is* someone with the *same* problem as me. It means the problem is reproducible - always good when you need to track down a weird problem. Rob: -) -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of CLEMENT Francis Sent: Thursday, September 01, 2005 5:34 PM To: 'xmail@xmailserver.org' Subject: [xmail] Re: messages to yahoo and or hotmail does not get delivered > -----Message d'origine----- > De : Rob Arends [mailto:[EMAIL PROTECTED] > Envoyé : jeudi 1 septembre 2005 01:53 > À : xmail@xmailserver.org > Objet : [xmail] Re: messages to yahoo and or hotmail does not get > delivered > > > > Francis,=20 > > This is the exact error I have had before. I have the same setup - > your > *whole* description below is *exactly* what I have. I have had this = > problem while on 1.15 & 1.17 also. However at the time though, I did > not know = why my emails were failing. I don't remember exactly if we encourated the problem with 1.17 (seams not in my mind) (but can be explained because we didn't had many traffic directed to hotmail at 1.17 time) > The only difference is that I have not had an issue with hotmail, = > usually it is with some other domains. Perhaps my users don't send to > hotmail as = much. > I have not had the time to debug it to an absolute end and offer > proof, = and so the previous thread died. > > I have tracked it down to the fact that every domain that I have had > problems with has had an A record for the domain & that A record = > resolves to a different IP than that of the MX record. This in itself > is True > not a DNS > problem (normal dns operation). But I have found that clearing > xmail's = dns cache & restarting xmail resolves the problem for a > while. IIRC just restarting xmail might be enough. Yes The problem is EXACTLY 'XMAIL comes back to the A record for obscur reasons (internal or due to bad dns responses ?) even if MX records exists for the target domains'. > > I actually used the SmartDNSHost only *after* I have troubles with MX > & = A records, but while the problem *seems* to have reduced, it has > not gone. > > It does seem to be a logic issue in xmail's mx resolving code, but I = > have no proof. In my current configuration, xmail 1.21 forwarding ALL traffic to a Symantec SMTP AV Gateway USING the SAME Microsoft DNS SERVERS, then ALL TRAFFIC IS OK (except usual errors, timeouts, ...) In another 'old' configuration, we used a Microsoft (yes!) Iis SMTP server using the same dns sservers and all was ok too !! > I expect that an Ethereal trace before and after is the only thing > that = can be done to prove it. > I have to get time to get them ... > Hopefully this info will help someone that has the time & the symptoms > = to get to the bottom of it. > > Rob :) > Francis - 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] - 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]
