You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@spamassassin.apache.org by Patrick Sneyers <cg...@bulckens.com> on 2007/03/12 09:24:37 UTC

helo_ip_mismatch - please explain.

Could someone explain why this got triggered?
Message looks to be pretty OK. Sent from a DSL client (behind NAT)  
through ISP's SMTP.


4.0 RCVD_HELO_IP_MISMATCH Received: HELO and IP do not match, but should

Received: from outmx010.isp.belgacom.be ([195.238.5.233] verified)
   by domain.com (CommuniGate Pro SMTP 5.1.7)
   with ESMTPS id 2614512 for user@domain.com; Fri, 09 Mar 2007  
15:30:52 +0100
Received: from outmx010.isp.belgacom.be (localhost [127.0.0.1])
         by outmx010.isp.belgacom.be (8.12.11.20060308/8.12.11/Skynet- 
OUT-2.22) with ESMTP id l29EUY7w010372
         for <us...@domain.com>; Fri, 9 Mar 2007 15:30:34 +0100
         (envelope-from <se...@domain.com>)
Received: from 1.0.0.16 (253.174-201-80.adsl-dyn.isp.belgacom.be  
[80.201.174.253])
         by outmx010.isp.belgacom.be (8.12.11.20060308/8.12.11/Skynet- 
OUT-2.22) with SMTP id l29EUNvJ010117
         for <us...@domain.com>; Fri, 9 Mar 2007 15:30:24 +0100
         (envelope-from <se...@domain.com>)


Patrick Sneyers
Belgium

Re: helo_ip_mismatch - please explain.

Posted by Patrick Sneyers <cg...@bulckens.com>.
Op 12-mrt-07, om 15:02 heeft Matt Kettler het volgende geschreven:

> Patrick Sneyers wrote:
>> Could someone explain why this got triggered?
>> Message looks to be pretty OK. Sent from a DSL client (behind NAT)
>> through ISP's SMTP.
>>
>>
>> Received: from 1.0.0.16 (253.174-201-80.adsl-dyn.isp.belgacom.be
>> [80.201.174.253])
>>         by outmx010.isp.belgacom.be
>> (8.12.11.20060308/8.12.11/Skynet-OUT-2.22) with SMTP id  
>> l29EUNvJ010117
>>         for <us...@domain.com>; Fri, 9 Mar 2007 15:30:24 +0100
>>         (envelope-from <se...@domain.com>)
> From the looks of things, the client "HELO'ed" as "1.0.0.16"
>
> SA tries to detect HELO's that are part of the private-ip ranges
> reserved by RFC 1918 for NAT and other such uses, and will ignore  
> those.
>
> However, 1.0.0.16 is NOT a valid IP address to be using for NAT.  
> That IP
> range is IANA reserved.
>
> So, SA is winding up dinging them because their NAT is invalid. If  
> their
> NAT was valid, SA would have ignored it.
>

Thank you for this explantion, clear as ever.
Patrick

Re: helo_ip_mismatch - please explain.

Posted by Matt Kettler <mk...@verizon.net>.
Patrick Sneyers wrote:
> Could someone explain why this got triggered?
> Message looks to be pretty OK. Sent from a DSL client (behind NAT)
> through ISP's SMTP.
>
>
> Received: from 1.0.0.16 (253.174-201-80.adsl-dyn.isp.belgacom.be
> [80.201.174.253])
>         by outmx010.isp.belgacom.be
> (8.12.11.20060308/8.12.11/Skynet-OUT-2.22) with SMTP id l29EUNvJ010117
>         for <us...@domain.com>; Fri, 9 Mar 2007 15:30:24 +0100
>         (envelope-from <se...@domain.com>)
>From the looks of things, the client "HELO'ed" as "1.0.0.16"

SA tries to detect HELO's that are part of the private-ip ranges
reserved by RFC 1918 for NAT and other such uses, and will ignore those.

However, 1.0.0.16 is NOT a valid IP address to be using for NAT. That IP
range is IANA reserved.

So, SA is winding up dinging them because their NAT is invalid. If their
NAT was valid, SA would have ignored it.