See inline. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of CLEMENT Francis Sent: Tuesday, 23 May 2006 2:26 AM To: '[email protected]' Subject: [xmail] Re: xmail DNS problem : First sample
>-----Message d'origine----- >De : [EMAIL PROTECTED] >[mailto:[EMAIL PROTECTED] la part de Rob Arends Envoyé : >lundi 22 mai 2006 14:35 À : [email protected] Objet : [xmail] Re: >xmail DNS problem : First sample > > Notice that I sayed that I don't use anymore smartdnshost : I hadn't. But all that means is that the local DNS is not at fault -and- that there lies something to be tweaked in the Xmail dns resolver / cache / resend logic. >The strange think is that if I stop xmail, clear xmail dns cache (even if cache is good) and restart xmail, sending new mail to >ifrance.com is then ok .... (not sure that this will become ok in all stop/clear/start cases, but at time I tried this, it was ok) I have seen this (was a couple of versions ago), and in fact just stop/start xmail was enough to allow delivery. >IMHO, it is simply not the 'job' of a mail server program to 'resolve, >cache, ...' dns queries ;) and it should let the local os resolver do the >job. >At least, I don't think caching the resulting dns query for future use >really 'enhance' the response time for 'delivery' as in many cases the >responding dns server (in most cases local or isp dns) do some cache by >itself (especially true when using 'smartdnshost'). I agree, on failure, the xmail dns cache must be ignored. The reason xmail cannot connect to remote server could be a problem with dns. And when using 'smartdnshost', there is less reason to have an xmail dns cache altogether. Note that on xmail servers that don't have dns timeout issues (assuming this is the cause) then they would never see the problem, because xmail always gets the MX records first time. In summary of this thread, I believe: 1. The cause of Xmail getting an A record when MX records exist is due to dns timeouts 2. The cause of Xmail not being able to send on next attempt is due to xmail using its dns cache regardless of previous send failure. 3. The local Xmail dns caching is still used when using 'smartdnshost'. 4. Possibility of xmail needing restart to clear some internal memory of previous mx lookups. I would like to ask for the following bug-fixes: 1. Xmail should ignore it's dns cache & re-resolve the domain, if this is not the first try to send this email. 2. Either have an option to disable the xmail dns cache, or disable it automatically when 'smartdnshost' used. This could be a tri-state switch 0,1,2. or off,on,auto - auto being off when smartdnshost=true, and on when smartdnshost=false. Rob :-) - 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]
