-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
In message <[email protected]>, Vittorio
<[email protected]> writes
>Whatever the adoption rate, there will be a long period in which DKIM2 and non-
>DKIM2 nodes share delivery paths:
No ... if the adoption rate is high then it will not be a long period !
If you currently sign with DKIM1 then signing with DKIM2 merely means
that you need to update your software (and perhaps change a config file)
At present you need to update your software most months to deal with
security issues (and Claude and his friends are rapidly changing months
to weeks). That is updating is not an unusual thing to do.
Note that we have carefully arranged that the hard bit -- changing your
DNS records -- is not required to update to DKIM2.
>DMARC's "adopt it", as I have noted before, was a single DNS
>record, required nothing of intermediaries, and even so took years
Though will you note that the take-up rate for DMARC increased markedly
when major mailbox providers decided that they would not tolerate large
flows of unauthenticated email any more.
Their tolerance of DKIM-replay is currently wearing very thin -- so you
might well see significant encouragement from them for senders to adopt
a system that prevents it.
- --
richard @ highwayman . com "Nothing seems the same
Still you never see the change from day to day
And no-one notices the customs slip away"
-----BEGIN PGP SIGNATURE-----
Version: PGPsdk version 1.7.1
iQA/AwUBapGFfWHfC/FfW545EQJ6OwCdEIB15WvYzRvspmapPR5S6/mjqBgAoJHR
CKxfTYhUVuJXCe4/C9fJluqP
=AYyF
-----END PGP SIGNATURE-----
_______________________________________________
Ietf-dkim mailing list -- [email protected]
To unsubscribe send an email to [email protected]
