SPF Fails on SA 3.0rc5 because of lack of HELO ?

[Avi Shatz <ls...@bquest.org>]

Hello there,

 

Recently I've tried installing SA 3.0rc5, and I wanted to try out its
SPF support on windows.

>From some reason, SPF is always claiming the lack of HELO in the
received headers, while they are clearly there.

 

I've made several tests to make sure of this like:

 

telnet mailserver.localmta.org 25

ehlo blabla

[...]

Quit

 

And the resulting Received: header contained that ehlo string
("blabla"), and not the rDNS.

 

Even with this mailing list I get "Received: from mail.apache.org
([209.237.227.199]) by localmta.org with Microsoft SMTPSVC(6.0.3790.80);
Sun, 19 Sep 2004 02:53:23 +0300" 

 

Where the rDNS of 209.237.227.119 is "hermes.apache.org", which brings
again to the conclusion it's the EHLO string, and it was missed by SA.

 

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

 

 

Any help would be appreciated :-)

 

Yours,

Avi