mail-vet-discuss
[Top] [All Lists]
<prev [Date] next>
[Advanced]
 <prev [Thread] next>

Re: [mail-vet-discuss] Last Call: draft-kucherawy-sender-auth-header (Message Header Field for Indicating Message Authentication Status) to Proposed Standard

2008-11-24 17:09:40
from [J D Falk] [Permanent Link] 
On 24/11/2008 13:13, "Dave CROCKER" <dhc(_at_)dcrocker(_dot_)net> wrote:


SM wrote:

   You are looking at
this header as attaching a trust assertion to the message instead of
a way for the MUA to receive the results from an upstream MTA that
perform the tests.


This is nicely written and exactly captures the key point of distinction about
this kind of authentication.


+1



_______________________________________________
NOTE WELL: This list operates according to 
http://mipassoc.org/dkim/ietf-list-rules.html
[More with this subject...]
<Prev in Thread] Current Thread [Next in Thread>
Previous by Date:  Re: [mail-vet-discuss] Last Call: draft-kucherawy-sender-auth-header (Message Header Field for Indicating Message Authentication Status) to Proposed Standard, Dave CROCKER
Next by Date:  Re: [mail-vet-discuss] Last Call: draft-kucherawy-sender-auth-header (Message Header Field for Indicating Message Authentication Status) to Proposed Standard, Douglas Otis
Previous by Thread:  Re: [mail-vet-discuss] Last Call: draft-kucherawy-sender-auth-header (Message Header Field for Indicating Message Authentication Status) to Proposed Standard, Dave CROCKER
Next by Thread:  Re: [mail-vet-discuss] Last Call: draft-kucherawy-sender-auth-header (Message Header Field for Indicating Message Authentication Status) to Proposed Standard, Douglas Otis
Indexes:  [Date] [Thread] [Top] [All Lists]