It appears that Wei Chuang  <[email protected]> said:
>-=-=-=-=-=-
>
>What about keeping the DKIM2 exclusion of X- header fields, and
>standardizing a new prefix for proprietary headers that can be optionally
>protected? 

The current plan is to sign everything except X-* and a short list of trace 
headers.

So if you add:

Google-secret-sauce: 42swordfish

that'll get signed.

I don't see a problem here to be solved.

R's,
John

_______________________________________________
Ietf-dkim mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to