|Main Archive Page > Month Archives > spamassassin-users archives|
>> X-Envelope-From: <email@example.com>
>> Received: from S253906HZ1EW06.usstls6-hosting.savvis.net (unknown
>> Is it because there is no reverse DNS entry?
> As the documentation  clearly states, the second value (a) is a
> string matched against the relay's rDNS in the Received headers, and
> (b) it is your MX's responsibility to perform the rDNS lookup and add it
> to the header.
> The latter is key, because despite "no reverse DNS entry" being
> ambiguous, there actually is an rDNS entry for the IP. In DNS, it's
> merely missing from the Received header.
> $ host 220.127.116.11
> 18.104.22.168.in-addr.arpa domain name pointer Lanyon.com.
> So, fix your MX. :) With an rDNS entry in the header, you will need to
I'm not it's a problem with my system. It's not that IP that has the
problem, but with the host itself:
$ host S253906HZ1EW06.usstls6-hosting.savvis.net
Host S253906HZ1EW06.usstls6-hosting.savvis.net not found: 3(NXDOMAIN)
I suppose I could add that host to /etc/hosts, but is there another
way to whitelist mail from this host/domain to a specific user? There
are also no SPF records to use...