rejected
You've been directed here by BlockSmith® —
the firewall forged by DTL to protect customers
and computers against spam and intruders.
(If none of this makes any sense to you, please copy the address of this web page and send it to your IT person. This page is intended for IT professionals. Hopefully, yours will know what to do.)
Why is this important?
Your mail server's IP address does not have a required DNS PTR record. This is bad.
Missing and/or non-matching forward and reverse DNS records are illegal for mail servers and you may have trouble sending mail to some Internet mail servers. Your server could even be blacklisted by DNS RBLs (realtime blackhole list services).
RFC1912 emphasizes the importance of this in section 2.1 Inconsistent, Missing, or Bad Data (http://tools.ietf.org/html/rfc1912):
“Many services available on the Internet will not talk to you if you aren't correctly registered in the DNS. Make sure your PTR and A records match. For every IP address, there should be a matching PTR record in the in-addr.arpa domain.”
Mismatched DNS records is admonished in this article (http://en.wikipedia.org/wiki/Forward-confirmed_reverse_DNS) stating:
“...there is no excuse not to have this set correctly under any legitimate circumstances.”
Simple steps to fix your problem:
- Fix.
Assign a DNS PTR value for your server's IP address, such as smtp.yourdomain.com, and then create a matching A record for "smtp.yourdomain.com" with the same IP addresss.
You may need to contact your ISP or server hosting company to request a PTR record change as they likely control the DNS for your server's IP address space. (Tip: Ask them to delegate your subnet IP space to your DNS server so you can make these changes yourself.) - Verify.
Use this tool to check your mail server's IP address and make sure it has a valid PTR record with a matching reverse DNS record:
http://multirbl.valli.org/fcrdns-test/211.187.226.131.html
(You can also revisit this page provided your DNS changes have had time to propagate to us.) - Unblock.
Once you have corrected your DNS records, you need to clear your mail server's IP address from our firewall, which you can do here:
http://ip.dtl.net?ip=211.187.226.131
(Don't bother to do this until you've completed the previous steps first because your server will simply get firewalled again.)
If you are unsuccessful with these steps contact DTL for assistance. Thank you for following the rules!
If you don't want to fix your problem...
Enforcement between properly configured SMTP servers is becoming more desirable by email system administrators to fight against spam. We have found that nearly 50% of the spam we reject comes from servers with broken DNS records. We encourage you to honor good email server practices by correcting your DNS records.
However, in some permittable cases, we can whitelist your server's IP address if you specifically request whitelisting by contacting us.
But only having us whitelist your server does not avoid email rejection from other servers that enforce connections with properly configured mail servers. In other words, this is something you'll need to deal with eventually. Why not now?