On 2/8/2018 9:09 AM, John R. Levine wrote:
They seek to distinguish important differences in processing for what
is claimed to be the /same/ protocol.
Except really they don't.
Except when they do. I'm thinking, f'rinstance, that there is a bunch
of code in things like Spamassassin that looks at headers and switches
out to routines to do stuff with them. There is nothing in Spamassassin
that needs to care whether a DKIM signature is v=1 or v=2, that's all
inside the DKIM library. If it passes a v=2 signature to a library that
only knows about v=1, the library will say it's invalid, which isn't
ideal but isn't wrong.
the code that tests for the v= parameter could, just as easily, check
for the presence of the new features.
NOTE WELL: This list operates according to