-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Frank Ellermann wrote:
Hi, the Internet Draft specifying a new header field Authentication-
Results is almost ready.
Well, good to know!
AFAIK the author intends to fix his "results" table:
Sender ID will get the same "smtp.helo" row as SPF, and there won't be a
separate "smtp.ehlo" row for SPF.
Good. The current table in draft-kucherawy-sender-auth-header-09 seems
weird in those regards.
Actually there is no difference between Sender ID and SPF wrt
"smtp.mfrom" and "smtp.helo" results, the draft could unify these rows.
Sender ID RFC 4406 got a normative reference to SPF RFC 4408 about this.
Agreed.
IMO the "security considerations" have to state that noting "hardfail"
results instead of simply rejecting "hardfail" will cause the loss of
legit mails in some arguably broken scenarios.
You mean "loss" as opposed to "no delivery, but sender gets a bounce"?
Assuming the author fixes this, can we "officially" support his draft,
on behalf of th SPF project ? The "iprev" check in this draft is quite
interesting, and the draft might also help the SSP-folks ("SSP" is the
keystone of DKIM).
I'm all for it. Have been since day 1. This unified header field is the
way to go.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFHTf+cwL7PKlBZWjsRAmT9AKDOUynb5rc1+owjLAAAjUONndDhdACfe5R1
Ev80kjSNBGklDzdhdnLdP9U=
=XdjH
-----END PGP SIGNATURE-----
-------------------------------------------
Sender Policy Framework: http://www.openspf.org
Archives: http://v2.listbox.com/member/archive/735/=now
RSS Feed: http://v2.listbox.com/member/archive/rss/735/
Modify Your Subscription:
http://v2.listbox.com/member/?member_id=2183229&id_secret=69941896-46c2b9
Powered by Listbox: http://www.listbox.com