Help - Bad Recipient Domain Does Not Exist Error!, Email bounces incorrectly with error

[wizzydaz]

We run Xmail V1.25 on a Windows 2003 Server.

One of our users is receiving a bounce message with the error as follows:

[<00>] XMail Bounce:
Rcpt=[name removed];Error=[Recipient domain "removed" does not exist (or it has a misconfigured DNS)]

The problem is that this domain does exist and is correctly configured.


I have accessed the server desktop and executed NSLOOKUP which returns 2 valid MX records. Using Telnet on each server on port 25, I find that the connections work.

I have sent a test message by hand via telnet, which is queued by the destination server. I have then sent a test email through the XMAIL instance running on the same server, but XMAIL still generates the bounce.

I have also searched the MX dns cache and found that the correct details were listed beneath the number 300. On erasing this file and restarting XMAIL I find that the cache file has not been regenerated.

Does anybody know what could be happening? The only thing that we can see is that the domain in question has a hyphen in the middle, but surely that can't be it.

Thanks in advance for your help.

Daz

[hschneider]

Pls post your server.tab

[wizzydaz]

I think we've found the problem.

Seems the recipient domain has a very strange DNS setup which requires a great many DNS lookups.

Setting the Xmail 'DNS smart host' option to our local BIND DNS server (which will do recursive lookups) seems to have solved the problem.

The strange thing is that the network connection properties for the server point DNS to the same local DNS server. Could it be that XMail ignores this and does it's own DNS lookups right from the root servers???

Thanks for your interest, Harald.

Darren

[hschneider]

XMail uses the DNS servers from the dnsroots file, which holds the root servers by default.
Entering your ISPs DNS in dnsroots should do the same as using smartdns.

[btech]

Hi Harald -

I am having the same problem ("Recipient domain "xxx.com" does not exist (or it has a misconfigured DNS)") - clearing the xmail DNS cache solves it temporarily in some cases but not in all, but then it begins again. This had only been a problem since upgrading to 1.25 (that I am aware of). Nothing in my configuration has changed from the previous version (1.24) and nothing in my DNS since way back (1.21?).

Domains I know to be valid via checks, and that are seen as valid locally by the system running XMail, still generate the "Recipient domain "xxx.com" does not exist (or it has a misconfigured DNS)" regularly. This has happened with more than 6 different but valid domains that test OK via dig or dnstools.com, etc.

I have nothing in SmartDNSHost (it is commented out of server.tab) nor have I ever. I am running FreeBSD 6.3 release. DNS is provided via my ISP's external DNS servers. More specifically, the server itself queries a M0n0wall router on the LAN which provides the DNS to the server and gets it's DNS from my ISPs servers, which is unchanged from previous versions of XMail where I did not see this problem. Everything is working aside from XMail (httpd, sshd, DoveCot, etc.)

Also, after a bit of research, I found: http://www.mail-archive.com/xmail@xmailser...g/msg15882.html and http://www.nabble.com/ErrCode--40-vs--215-td14108373.html

Neither seems to clearly pertain or help in my case. I also noted the error "Maximum DNS quesry depth exceeded" just now, and so I tried a DIG/Trace from the server running XMail to see what was up. It looks fine (I replaced the actual domain with xxx.com):

nosferatu# dig xxx..com mx +trace

; <<>> DiG 9.3.4-P1 <<>> xxx.com mx +trace
;; global options: printcmd
. 857 IN NS l.root-servers.net.
. 857 IN NS m.root-servers.net.
. 857 IN NS a.root-servers.net.
. 857 IN NS b.root-servers.net.
. 857 IN NS c.root-servers.net.
. 857 IN NS d.root-servers.net.
. 857 IN NS e.root-servers.net.
. 857 IN NS f.root-servers.net.
. 857 IN NS g.root-servers.net.
. 857 IN NS h.root-servers.net.
. 857 IN NS i.root-servers.net.
. 857 IN NS j.root-servers.net.
. 857 IN NS k.root-servers.net.
;; Received 500 bytes from 192.168.1.1#53(192.168.1.1) in 13 ms

com. 172800 IN NS a.gtld-servers.net.
com. 172800 IN NS b.gtld-servers.net.
com. 172800 IN NS c.gtld-servers.net.
com. 172800 IN NS d.gtld-servers.net.
com. 172800 IN NS e.gtld-servers.net.
com. 172800 IN NS f.gtld-servers.net.
com. 172800 IN NS g.gtld-servers.net.
com. 172800 IN NS h.gtld-servers.net.
com. 172800 IN NS i.gtld-servers.net.
com. 172800 IN NS j.gtld-servers.net.
com. 172800 IN NS k.gtld-servers.net.
com. 172800 IN NS l.gtld-servers.net.
com. 172800 IN NS m.gtld-servers.net.
;; Received 491 bytes from 199.7.83.42#53(l.root-servers.net) in 50 ms

com. 900 IN SOA a.gtld-servers.net. nstld.verisign-grs.com. 1202593831 1800 900 604800 900
;; Received 104 bytes from 192.5.6.30#53(a.gtld-servers.net) in 104 ms

Any ideas? Should I try SmartDNSHost to see what happens?

Thanks,
Jeff

[hschneider]

Try SmartDNS. If it fails, then forward this issue to Davidel at xmailserver.org. Pls include the real domain name, so he can track things down.