Hi David - I think I have finally solved this mysterious problem, and of course it was an element I had not even considered (as it often is). The line provider (Covad) for this server had a problem several weeks ago with this line, about the time I was updating xmail to 1.25. When they were running tests on the line, they had slowed it down (from 5.4mb down/700k up to 300k down/60k up) and they managed to leave it that way. By some miracle the people using this server didn't notice (nor did I), aside from this problem, as it also provides web services - it does explain a lot of "strange" behavior I have been seeing, though!
This slowdown seems to have been causing a time out on the DNS query for certain domains, so the common denominator may have been (just guessing) a high latency on the response time for these particular domains coupled with the very slow line speed of my servers connection, causing the fore mentioned error (NXDOMAIN). Now that the circuit is operating at its proper speeds, the problem has gone away. I don't know if this is a reflection on any particular package (Bind under *BSD, XMail, etc.) in terms of low speed testing, but it might be worth noting for someone that at very low speeds something is failing intermittently. Thanks for your help and input! Jeff David Lord wrote: > On 18 Feb 2008, at 12:27, Jeff Buehler wrote: > > >> Hi all - >> >> Sorry to be late to the game with this - in an earlier list email that I >> inadvertently deleted (thinking I had no helpful input, of course!) >> titled "Problem with XMail on NetBSD-4" there was a discussion about the >> error: >> >> Recipient domain "xxxx.com" does not exist (or it has a misconfigured DNS) >> >> I am also getting this error regularly with FreeBSD 6 and XMail 1.25. I >> mention it in the XMail forums as well, and read about a number of other >> recent occurrences, but nothing has been resolved specifically. As I >> mention in the forums, I have verified the domains are valid and >> properly configured in some of the cases, but the errors are consistent >> with specific domains. In my case, one example is "trikorausa.com" >> which I can send email from any server other than my active XMail server >> under FreeBSD, adn which looks properly configured via dnstools.com (I >> configured it, so I believe it is correct...) >> >> Davide responded: >> >> I think XMail is getting a ERR_DNS_NXDOMAIN (NXDOMAIN) from your DNS >> server. When that's happening, XMail does not even try to fall back to the >> A record delivery. >> >> and I think seems like it may be correct, but I am uncertain how to test >> this. The server does not provide DNS queries for itself (although it >> provides DNS for the domains it is authoritative on) but queries a >> m0n0wall router on the LAN, which queries my ISPs DNS servers. The >> server is able to resolve a dig as well as dig+trace to the MX record to >> trikorausa.com (and other domains) without incident. This would suggest >> that something else might be going on, since the domain does have a >> functional and valid MX record, so there should be no need to fall back >> to an A record. >> > > Davide's reply was in response to my problems with NetBSD-3.1 and > NetBSD-4.0. I'd been using SmartDNSHost pointing to my local dns as > that was also configured for private ips on the lan and at some point > this had become replaced by a malformed version (I'd commented out it > out for some reason and afterwards un-commented the wrong line). The > only thing this broke was local mail delivery which I didn't notice > until testing new server which used cloned configuration of current > server. > > >> This seems to be a new problem, but I updated XMail to 1.25, FreeBSD >> (minor update) and the m0n0wall router (minor update) all around the >> same time. I am not using SmartDNSHost, nor have I ever, although I've >> been running XMail for 6 or more years... should I test setting it to my >> ISP DNS servers rather than the local m0n0wall router (which queries the >> ISP servers anyway successfully with other services on the same server)? >> >> Does anyone have any ideas or recommendations about how to test where >> the problem might be? >> > > I'd suggest trying with SmartDNSHost set to the router then again > with it set to the ISP. > > What servers do you have set in resolv.conf? > > David > > > >> Thanks, >> Jeff >> > > - > 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]
