Subject: [spf-discuss] solving the forwarding problem
just some thoughs on how to resolve the forwarding problem without
having to wait for everybody to use SRS:
you mean the forwarding problem where they deliberately forge the envelope
from address? why isn't the envelope from the forwarders (list) address, ie
a 'real' unforged one that would pass SPF?
what does this break at the client end that is forcing the forwarders (list
servers) to forge the envelope from address in the first place? how many
mail clients actually display the envelope from to the user and not just the
data from/to/cc/bcc? or is it a lack of configuration options in
forwarers/list servers?
-------
Sender Policy Framework: http://spf.pobox.com/
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/?listname=spf-discuss(_at_)v2(_dot_)listbox(_dot_)com