-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
David MacQuigg wrote:
The Milter API allows the Milter to "insert" a header at any position in
the existing header stack. It seems to me we should follow a simple
rule - prepend every new header in exactly the order it is generated.
If the SPF check is done before the body of the message is received, it
ought to go just below the Received: header.
You seem to assume that the usual "Received:" header is generated only
after the body has been received. There is, however, not a single RFC out
there mandating that. There is no defined point in time when the
"Received:" header must be generated.
Thus it would be most logical to always generate the "Received:" header
first, before any other trace headers. The "Received:" header is a well-
known, trusted concept understood by many e-mail header parsers, and thus
it is the best authority for a message's transport path for the purpose of
message parsers such as SpamAssassin. All other headers should be added
above of it so that parsers can be certain that they belong to the same
hop as the trusted "Received:" header.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
iD8DBQFFVggPwL7PKlBZWjsRApbvAKDOO76genRD4BgEsEq6mWYYKYzb/QCcC7fH
yl7JRlq+aPgJCXWGDZ8TTfo=
=Vcse
-----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