Well, the way that Microsoft SMTP works here, is if the line is:
Received: from frontend1.messagingengine.com ([66.111.4.30]) by
localmta.org with
Microsoft SMTPSVC(6.0.3790.80); Sat, 18 Sep 2004 19:53:03 +0300
The EHLO is: "frontend1.messagingengine.com"
The IP is: 66.111.4.30
The accepting Server is: localmta.org
I've double checked this, that first string is not the rDNS, its clearly
the EHLO, and can be used..
Any ideas on how to solve this?
-----Original Message-----
From: Avi Shatz
Sent: Sunday, September 19, 2004 2:18 AM
To: 'Loren Wilton'
Subject: RE: SPF Fails on SA 3.0rc5 because of lack of HELO ?
Well, the way that Microsoft SMTP works here, is if the line is:
Received: from frontend1.messagingengine.com ([66.111.4.30]) by
localmta.org
with
Microsoft SMTPSVC(6.0.3790.80); Sat, 18 Sep 2004 19:53:03 +0300
The EHLO is: "frontend1.messagingengine.com"
The IP is: 66.111.4.30
The accepting Server is: localmta.org
I've double checked this, that first string is not the rDNS, its clearly
the EHLO, and can be used..
Any ideas on how to solve this?
-----Original Message-----
From: Loren Wilton [mailto:[EMAIL PROTECTED]
Sent: Sunday, September 19, 2004 2:01 AM
To: users@spamassassin.apache.org
Subject: Re: SPF Fails on SA 3.0rc5 because of lack of HELO ?
> From some reason, SPF is always claiming the lack of HELO in the
received
headers, while they are clearly there.
Nope, they're not.
>I'm attaching an example message file which I try to pass via
spamassassin,
and get something like:
>debug: SPF: checking HELO (helo=, ip=66.111.4.30)
>debug: SPF: trimmed HELO down to ''
>debug: SPF: cannot get HELO, cannot use SPF
Received: from frontend1.messagingengine.com ([66.111.4.30]) by
localmta.org
with
Microsoft SMTPSVC(6.0.3790.80); Sat, 18 Sep 2004 19:53:03 +0300
Received: from web4.messagingengine.com (web4.internal [10.202.2.213])
by
frontend1.messagingengine.com (Postfix) with ESMTP id 19E5CC154AE
for
<[EMAIL PROTECTED]>; Sat, 18 Sep 2004 12:53:00 -0400 (EDT)
Those debug lines are pointing to the first received line above. The
HELO
name would normally appear between the ( and the [ of the dotquad
address.
Nothing there.
The second received line does appear to have a HELO name on it.
However,
the address is in private space, so is not usable.
Loren
