Frank Ellermann writes:
If you'd think that your document already is the "mfrom"
specification, how comes that folks like Dick or the MAAWG
still have doubts about HELO ?
Speaking for myself, it's a matter of interpretation. As I see it,
the SPF draft defines two scopes, an mfrom scope and a helo scope and
says to switch to the helo scope if the mfrom is empty. The SenderID
core draft incorporates the SPF mfrom scope by explicit reference, but
I do not see that as including the switch to a helo scope. Wayne
doesn't agree with that view, and the SenderID authors aren't around
or aren't speaking up. However, the SenderID draft explicitly allows
for additional scopes and even gives some requirements they must meet.
--
Dick St.Peters, stpeters(_at_)NetHeaven(_dot_)com
-------
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/?listname=spf-discuss(_at_)v2(_dot_)listbox(_dot_)com