Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

What to do? It blocks almost all incoming messages. What to do? It complains about:

  • RDNS_NONE - a host with no rDNS? What is that?

What does these rules mean really?

share|improve this question
up vote 0 down vote accepted

I'm gonna guess this is spamassassin.

  • RDNS_NONE means it couldn't perform a reverse-DNS lookup on the originating SMTP server
  • BAD_ENC_HEADER is whitespace in the encoded part of the message
  • FH_DATE_PAS_20XX means the timestamp of the message is way off in the future.

You can disable RDNS lookups but you'll be reducing security somewhat. Check your system time is accurate on all the servers involved. Check the email that is arriving hasn't already been run through spamassassin before it reaches your spamassassin server, as that triggers the ENC_HEADER rule.

share|improve this answer

You should have automatic rules updates for your spamassassin server. FH_DATE_PAS_20XX used to add a +3 score to everything in 2010 or later; since we're in 2010 you likely didn't update your rules and you're adding a +3 score to all current emails!

The updated rules changes this to anything in 2020 or later, IIRC.

Regarding the RDNS_NONE tag, make sure you can reverse-resolve the IPs of the servers you get emails from. If you have a frontend server that do not resolve or broken DNS resolver this may explain it.

share|improve this answer
Thanks for your answer! – jack Feb 17 '10 at 9:49

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.