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 ? Francis -----Message d'origine----- De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] la part de Davide Libenzi Envoy=E9 : mardi 19 f=E9vrier 2008 21:33 =C0 : XMail mailing list Objet : [xmail] Re: FreeBSD problem (similar to NetBSD problem reported earlier?) On Tue, 19 Feb 2008, Jeff Buehler wrote: > Hi Davide - >=20 > Everything works when I use SmartDNS host to point to the same = resolver=20 > as the server uses (a m0n0wall router). > If I do not use SmartDNS host, I get the error to domains that can=20 > receive email from other sources. >=20 > One example domain is trikorausa.com, although I am getting reports = of=20 > the error from clients with about 5 other domains that mail can be = sent=20 > to from other sources (like Hotmail). The results of a dig=20 > trikorausa.com mx +trace actually result in a "dig: too many lookups" = > failure - apparently the last time I did it a inadvertently did a = "dig=20 > trikorausa.com mx + trace" with a space between the + and the trace = and=20 > didn't notice that it hadn't performed a trace - sorry about that... >=20 > I will research why would I might get a "too many lookups" failure = (the=20 > domain is fine and has valid MX records) and try to determine what = may=20 > have changed recently (and if XMail is even involved) - I send to = this=20 > domain all of the time and this seems to have started about when I=20 > upgraded to 1.25. However, there were a number of changes around = that=20 > time (including a FreeBSD update) so I will continue trying to = isolate=20 > what is up and post back if I can find the problem. There's some configuration problem "inside" your network. The command = is=20 with "+trace" (w/out space), and from here is working fine. So it must be something internal to your net. - 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]
