> And since nothing is special about my own MS SMTPSVC (Win2k3 SMTP
> Server), I believe the behavior of received.pm should be changed to
> allow SA running on those machines to properly detect the EHLO
> string, and thus allow SPF Detection to properly execute.
So what *do* your mail headers look like when your HELO or EHLO argument
is not the FQDN of the connecting host? Most MTAs will VERY carefully
include these two pieces of information separately: sendmail for
instance, will show something like:
Well, lets say for instance the HELO string is "Hello_string"
Remote IP is: "11.22.33.44"
My mail server DNS is: "localmta.org"
And the receiving time is: Sat, 18 Sep 2004 19:53:03 +0300
The resulting received line would be:
Received: from Hello_string ([11.22.33.44]) by localmta.org with
Microsoft SMTPSVC(6.0.3790.80); Sat, 18 Sep 2004 19:53:03 +0300
Actually Received.pm already includes support for this MTA with this
line:
# Received: from inet-vrs-05.redmond.corp.microsoft.com ([157.54.6.157])
by # INET-IMC-05.redmond.corp.microsoft.com with Microsoft
SMTPSVC(5.0.2195.6624);
# Thu, 6 Mar 2003 12:02:35 -0800
if (/^from (\S+) \(\[(${IP_ADDRESS})\]\) by (\S+) with /) {
$helo = $1; $ip = $2; $by = $3; goto enough; }
Problem is that its never triggered, because of a previous *incorrect*
hit
