ietf-dkim
[Top] [All Lists]

Re: [ietf-dkim] z= question with X headers

2006-04-28 05:32:15

You can not avoid such ambiguities unless you can specifically reference the copied data as part of signed header field listing. That is why I went
with copying to make new header field and referencing that in my design.

On Thu, 27 Apr 2006, Tony Hansen wrote:

I also read it the same way Arvel did. Also, if it isn't interpreted
that way, you get ambiguities when multiple instances of a particular
header are listed and only some of the values are presented in z=. In
particular, the z= field is also supposed to help you work around header
reordering; you need all values to be there in order to do that.

        Tony Hansen
        tony(_at_)att(_dot_)com

Arvel Hathcock wrote:
The z= tag allows you to put as many or as few headers in it as you
want. I typically only put subject, from, to and maybe a few others
that I regularly see getting toasted.  Was this actually unclear? If
so it might make sense to be more explicit.

Mike, it could just be me being dense.  FWIW though this text was
understood by two of us here as meaning copy all the headers:

"A vertical-bar-separated list of header field names and copies of
header field values that identify the header fields present when the
message was signed."

Perhaps:

"A vertical-bar-separated list of select header field names and copies
of header field values that identify the header fields present when the
message was signed.  It is not required to include all header field
names and values."
_______________________________________________
NOTE WELL: This list operates according to http://mipassoc.org/dkim/ietf-list-rules.html