On Wed, 20 Feb 2008, CLEMENT Francis wrote: > Hello Davide > > Recently I asked you how SMARTDnshost variable affected xmail internal > resolver, and you said that when using SmartDnsHost, xmail only ask for = > the > 'final' request (directly the mx lookup without trying first soa, ns, = > .... ) > > I asked this because I had the same problem as Jeff but was not at this = > time > able to find the reason about xmail resolver without smartdnshost = > setting > able or not to find the mx records for domains that was ok with dig = > and/or > nslookups at xmail server side (so using os resolver) and that the same > xmail server with smartdnshost applied was able to find without = > problems > (with all involved dns servers caches cleaned that don't use smart = > hosts > themself) > > I didn't have time to trace dns queries w/wo SmarDnshost usage (to see > timings, ...) but it seems that in some cases of long latencies on the = > wire > (temporarly high bandwidth usages, ...) xmail 'timeouts' quicker for = > dns > queries than then it use 'classic' resolvers (SmartDnsHost setting in > effect). > The problem could be after this timeout : how xmail handle this ? retry > later ? and on persistent 'no response from dns server', flag the = > domain > with an 'nxdomain' internal error without having any valid 'nxdomain' > responses ? > Could any of these be possible ? > Any way to test xmail resolver by changing xmail internal dns 'timeout' > value ?
If there's a timeout, XMail will retry using the standard delivery policies. - 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]
