-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Arik Baratz writes:
I am so strongly against that. There is already a standard header to do
just that! Why reinvent it?
Reread this paragraph:
This would allow filters like SpamAssassin to pick up the envelope-from
used at each step of the chain, which is very valuable especially when
intermediate steps tend to rewrite it. (For example, fetchmail makes some
incorrect assumptions, and will add an *incorrect* Return-Path header if
an X-Envelope-From header exists, even from an earlier handover.)
Key phrase: "the envelope-from used at each step of the chain".
In this situation:
SENDER -> FORWARDER -> RECIPIENT
There is currently no way to find out what the env from was at FORWARDER
if it has been rewritten -- as it would be for a mailing list or an
SRS-compliant forwarder.
- --j.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)
Comment: Exmh CVS
iD8DBQFAGAmaQTcbUG5Y7woRAol+AJ9/0U2iEXD3GH3XQXnTJwMvgpojaQCeOGkf
zTcpKZ1TfYQx5B78qROMx0I=
=+BBV
-----END PGP SIGNATURE-----
-------
Sender Permitted From: http://spf.pobox.com/
Archives at http://archives.listbox.com/spf-discuss/current/
Latest draft at http://spf.pobox.com/draft-mengwong-spf-02.9.4.txt
Wiki:
http://spfwiki.infinitepenguins.net/pmwiki.php/SenderPermittedFrom/HomePage
To unsubscribe, change your address, or temporarily deactivate your
subscription,
please go to
http://v2.listbox.com/member/?listname(_at_)©#«Mo\¯HÝÜîU;±¤Ö¤Íµø?¡