It appears that Hannah Stern <[email protected]> said: >Hi! > >Why can, in your example, the changes mv=3 to mv=5 not be coalesced? >That ought to be not so difficult algorithmically.
That's a deliberate choice. The places that change messages and the ones that sign messages are often not the same, and this lets each apply a header describing what it did. An example would be a mailing list that adds a subject tag to a message and adds a M-V header saying what it did, then hands the modified message to an MTA that signs it and sends it out. While this makes the verifier a little more complicated, so what? Nearly everyone uses one of a handful of libraries to check the current DKIM signatures, and that will likely also be true for DKIM2. The people who write the libraries can deal with it, and mail system operators use the results returned by the libraries. R's, John _______________________________________________ Ietf-dkim mailing list -- [email protected] To unsubscribe send an email to [email protected]
