Sweet, so the TTL expired - that's where I thought the problem was - DNS timeouts.
So Davide, can you explain.... When the TTL expires and Xmail tries the A record, why then for ALL the retries, does xmail attempt to send to the same server? If the xmail re-resolved the domain for each retry, wouldn't it get the correct MX, now that the SmartDNShost has cached either NS/MX for the domain. I totally understand xmail can't do much if the smartdnshost can't resolve the MX, however usually it can on the second attempt, so xmail should be able to send the email on the second try. Rob :-) -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Davide Libenzi Sent: Sunday, 28 May 2006 6:39 AM To: '[email protected]' Subject: [xmail] Re: xmail DNS problem : First sample On Mon, 22 May 2006, CLEMENT Francis wrote: > An 'non-authoritatie answer' is usual as many isp's do local 'dns = > caching', and this is not a problem as long as the 'dns cache' > observes the = various refresh times of the zone. But yes it could be. > > Here when I do a nslookup from my xmail server, I don't get > 'non-authoritative answer' and get a list of mx for ifrance.com ... > And xmail mx cache file ifrance.com contains : > 86400 > 0:mailrecv.ifrance.com. > > ?!?!?! > So xmail resolver obtained the good mx response ! > So why xmail try to send the A pointer ? Because the TTL expired. - Davide - 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]
