Victor Sudakov wrote:
> 
> OK, this was a poor example. Here is a better one. Let's start anew :)
> 
> The rule is
> whitelist_from_rcvd [EMAIL PROTECTED] mncs.tomsk.ru
> 
> The relay is mncs.tomsk.ru, as you see, whose forward and reverse DNS
> mapping is correct.
> 
> Why does the rule not work with the message below?

An interesting observation. Below is the Received header and how it
was parsed.

Received: from mncs.tomsk.ru ([212.73.124.135] verified)
  by relay2.tomsk.ru (CommuniGate Pro SMTP 5.1.13)
  with ESMTP id 9786656 for [EMAIL PROTECTED]; Thu, 27 Mar 2008 15:08:17 +0600

[53938] dbg: received-header: parsed as [ ip=212.73.124.135 rdns= 
helo=mncs.tomsk.ru by=relay2.tomsk.ru ident= envfrom= intl=0 id=9786656 auth= 
msa=0 ]

I think the problem may be that 'rdns' is empty for some reason. But why
it is empty I don't know. Any ideas? Perhaps a bug in 
SpamAssassin/Message/Metadata/Received.pm ?

-- 
Victor Sudakov,  VAS4-RIPE, VAS47-RIPN
sip:[EMAIL PROTECTED]

Reply via email to