-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Dick St.Peters wrote:
What this doesn't take into account is *why* addresses are forwarded.
For example, a common forwarding use is "role" addresses, such as
"treasurer(_at_)organization(_dot_)org" where a new treasurer is elected
periodically, or "service(_at_)company(_dot_)com" where multiple people
receive
the mail. In the latter case, sending mail directly to a forwarding
destination address may result in a request sitting in the mailbox of
someone who is on vacation, when the request could have been handled
by any of the other service@ recipients.
Those are also the cases that are most relevant for the forwarder being
white-listed by the recipient. If julian(_at_)mehnle(_dot_)net is the
"treasurer
@organization.org", then he should trust organization.org and not subject
messages forwarded by them to SPF checking. Problem solved.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFFuq3nwL7PKlBZWjsRAncSAKDNP0863S86+wV6DyoMIcgMQqhFzwCdFahu
TTD/PBv1fLLfYdbB+F53cEU=
=swMo
-----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