In
<17349(_dot_)13698(_dot_)854265(_dot_)625572(_at_)saint(_dot_)heaven(_dot_)net>
"Dick St.Peters" <stpeters(_at_)NetHeaven(_dot_)com> writes:
wayne writes:
The "mfrom" scope in SenderID appears to be almost identical to to
SPFv1 records. It describes both the 2821.MAILFROM and 2821.HELO
identities, just like SPFv1.
I believe this is not correct. The strings "helo" and "ehlo" with any
mix of case do not appear in either SenderID draft. [...]
The core draft is ambiguous in that it defers description of the
MAIL-FROM test to your draft, but it does not say anything about the
HELO test from your draft being included, in spite of ample
opportunity to do so in various places in the core draft.
When the 2821.MAILFROM is empty, the mfrom test reverts to checking
the HELO domain. So, while SenderID doesn't explicitly allow you to
check the HELO domain all the time, it will check it some of the time.
As a result, all spf2.0/mfrom records need to deal with both
2821.MAILFROM and 2821.HELO scope requirements.
-wayne
-------
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