spf-discuss
[Top] [All Lists]

[spf-discuss] Re: Apache SpamAssassin SPF checks

2006-11-11 04:41:29
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Scott Kitterman wrote:
On Saturday 11 November 2006 01:25, Daryl C. W. O'Shea wrote:
Julian Mehnle wrote:
According to RFC 4408, section 7, the "Received-SPF" header "SHOULD
be prepended to the existing header, above the Received: field that
is generated by the SMTP receiver."
[...]
[...]

The current version of postfix-policyd-spf-perl supports this.

Are you sure that postfix-policyd-spf-perl actually makes "Received-SPF" 
headers appear _above_ the according "Received" headers??  That's what 
Daryl's argument was about.  "Received-SPF" headers being inserted _below_ 
the accorging "Received" headers seems to be commonly supported but, as he 
explained, isn't reliable for SpamAssassin's purposes.

[The current version of postfix-policyd-spf-perl is available on CPAN.]

No, it isn't.  The one included with M:S:Q 1.999.1 is version 1.06, which 
is old.  And M:S:Q will not get updated any longer.

PySPF supports received-spf. [...]

... inserting it _above_ the according "Received" header?

I haven't done any programming on Milters, but I believe that pymilter
adds the received header, [...].

... inserting it _above_ the according "Received" header?

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)

iD8DBQFFVbaRwL7PKlBZWjsRAjIMAJ9piVKYXF/GHqrrXqLhrklT7HPAsACgk9m+
vvw+U/54rSvZ7oJId+euL60=
=W3Qv
-----END PGP SIGNATURE-----

-------
Sender Policy Framework: http://www.openspf.org/
Archives at http://archives.listbox.com/spf-discuss/current/
To unsubscribe, change your address, or temporarily deactivate your 
subscription, 
please go to http://v2.listbox.com/member/?list_id=735