In
<Pine(_dot_)LNX(_dot_)4(_dot_)44(_dot_)0509011339130(_dot_)13796-100000(_at_)bmsred(_dot_)bmsi(_dot_)com>
"Stuart D. Gathman" <stuart(_at_)bmsi(_dot_)com> writes:
On Thu, 1 Sep 2005, wayne wrote:
There is currently no such thing as "spf2.0/helo".
No, but there ought to be, and the interpretation is obvious
(apply policy to HELO identity only).
HarryK, JimL and MarkL *really* didn't want the HELO stuff in
SenderID, hence it was deleted along with the %{h} macro.
Of course, anyone is free write up an I-D. It should be pretty easy
to take the current PRA I-D and modify it for HELO checking.
It would answer all the
real objections of the CSV/CSA people.
No, they would still object that SPF HELO checking requires more DNS
lookups and it doesn't yet have any accreditation support.
The record would be found
when looking for SPF/Sender-ID policies. One DNS lookup gets
senders choice of connect ip policy: HELO,MFROM,PRA or combination.
Ya know, I've ponder it several times, but I've never figured out the
semantic interactions between an "spf2.0/mfrom" record at the HELO
domain level and an "spf2.0/mfrom" record at the MAILFROM domain
level. If you throw in "spf2.0/helo" records, I'm not sure what
happens.
Something to think about.
-wayne
-------
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