[EMAIL PROTECTED] is sending a message through my server, mail.taisweb.net, to [EMAIL PROTECTED]
My log files show the following: SMTP (bb620b6e00fc1d1c) processing S:\imail\spool\Qbb620b6e00fc1d1c.SMD SMTP (bb620b6e00fc1d1c) [x] looking up e911.yanceycounty.org in HOSTS and MX SMTP (bb620b6e00fc1d1c) [x] looking up e911.yanceycounty.org by stack SMTP (bb620b6e00fc1d1c) [x] looking up e911.yanceycounty.org in HOSTS and MX SMTP (bb620b6e00fc1d1c) [x] looking up e911.yanceycounty.org by stack
This means that IMail can't get the MX record for e911.yanceycounty.org. There are *serious* problems with that domain.
http://www.dnsreport.com/tools/dnsreport.ch?domain=yanceycounty.org shows problems with the yanceycounty.org domain's DNS, and http://www.dnsreport.com/tools/dnsreport.ch?domain=e911.yanceycounty.org also shows (I believe) that there is no name server delegation for the e911 subdomain (I'm not sure of the terminology). What I believe is happening is that, because there is no "glue" at the tld name servers for the e911 subdomain, Imail is traversing the FQDN to try and find name servers for the e911 subdomain. This name server delegation does not exist. Am I correct?
Someone is about to jump on that "glue" thing -- it's safe to ignore that. What really matters is that they have an extremely bogus MX record -- see http://www.dnsstuff.com/tools/lookup.ch?name=e911.yanceycounty.org&type=MX . Their MX record is:
e911.yanceycounty.org. MX 12.21.162.24. [Preference = 10] e911.yanceycounty.org. MX 12.21.162.24. [Preference = 20] e911.yanceycounty.org. MX 12.21.162.24. [Preference = 30]
The first problem is that their MX records point to IPs, not hostnames, so it is impossible to send mail to them. MX records contain
hostnames. So if you try entering an IP, a mailserver will try contacting the DNS servers for the .24 TLD -- but there is no such TLD. The E-mail will therefore be rejected.
The second problem is that they are *very* clueless -- all three MX records point to the same location. Even if they had hostnames, this means that if a mailserver has trouble connecting, it has to try connecting to that IP 3 times, which is a waste of resources. It's clear that they have very little understanding of MX records.
There are more problems, but the first one here will prevent mail from getting delivered to them.
-Scott
---
Declude JunkMail: The advanced anti-spam solution for IMail mailservers since 2000.
Declude Virus: Ultra reliable virus detection and the leader in mailserver vulnerability detection.
Find out what you've been missing: Ask for a free 30-day evaluation.
--- [This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)]
To Unsubscribe: http://www.ipswitch.com/support/mailing-lists.html List Archive: http://www.mail-archive.com/imail_forum%40list.ipswitch.com/ Knowledge Base/FAQ: http://www.ipswitch.com/support/IMail/
