My local ISP (rcn.com) reconfigured their email servers. The
69.168.97.77 hop does not seem to be doing rdns lookups on the
previous hop. For example, I get these two received headers at the
trust boundary:
...
Received: from mx.rcn.com ([69.168.97.77])
by mx06.atw.mail.rcn.net with ESMTP; 20 Feb 2013 17:07:22 -0500
...trust/internal boundary...
Received: from [216.33.63.216] ([216.33.63.216:56326]
helo=bigfootinteractive.com)
by mx.rcn.com (envelope-from
<1709130a2layfovcia3kqqzqaaaaabnxydzhs2jc2h4yaa...@mail.ameriprise.com>)
(ecelerity 2.2.3.49 r(42060/42061)) with ESMTP
id 29/DB-26250-A1945215; Wed, 20 Feb 2013 17:07:22 -0500
...
and the relays are parsed as
X-Spam-Relay:
Trusted= ...[ ip=69.168.97.77 rdns=mx.rcn.com helo=mx.rcn.com
by=mx06.atw.mail.rcn.net ident= envfrom= intl=1 id= auth= msa=0 ]
Untrusted=[ ip=216.33.63.216 rdns= helo=bigfootinteractive.com
by=mx.rcn.com ident=
envfrom=1709130a2layfovcia3kqqzqaaaaabnxydzhs2jc2h4yaa...@mail.ameriprise.com
intl=0 id=29/DB-26250-A1945215 auth= msa=0 ] ...
This leads to various bad things (RDNS_NONE & broken WHITELIST_FROM_RCVD)
Is there anything in SpamAssassin that can deal more elegantly with
this particular problem? Perhaps Some sort of please_fill_in_rcvd_rdns
type option?
I'm still on 3.2.5 (yes I know it is old).
-jeff
