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

2004-09-25 Thread Avi Shatz
users@spamassassin.apache.org Subject: Re: SPF Fails on SA 3.0rc5 because of lack of HELO ? Avi Shatz wrote on Sun, 19 Sep 2004 18:13:43 +0300: > The only thing I wanted to prove with this is that line, that is > created by my local mail server (the last hop, and the most important > one for SPF

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

2004-09-20 Thread Avi Shatz
> 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 loo

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

2004-09-19 Thread Avi Shatz
2004 4:27 PM To: users@spamassassin.apache.org Subject: Re: SPF Fails on SA 3.0rc5 because of lack of HELO ? Avi Shatz wrote on Sun, 19 Sep 2004 02:52:49 +0300: > telnet mailserver.localmta.org 25 > ehlo blabla > What do you want to prove with this? What needs to happen is that [66.111

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

2004-09-18 Thread Avi Shatz
r than the rDNS lookup. {^_^} - Original Message ----- From: "Avi Shatz" <[EMAIL PROTECTED]> > > 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 > Mi

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

2004-09-18 Thread Avi Shatz
1.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' Sub

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

2004-09-18 Thread Avi Shatz
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'm attaching an example message file which I try to pass via