-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
At the end of January Dave Crocker posted a review of the then current
"-01" version of draft-gondwana-dkim2-motivation. This document has now
been split into an "-02" and draft-gondwana-dkim2-headers (-01).
Rather belatedly this is a response to that
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
At the end of January Dave Crocker posted a review of the then current
"-01" version of draft-gondwana-dkim2-motivation. This document has now
been split into an "-02" and draft-gondwana-dkim2-headers (-01).
Rather belatedly this is a response to that
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
At the end of January Dave Crocker posted a review of the then current
"-01" version of draft-gondwana-dkim2-motivation. This document has now
been split into an "-02" and draft-gondwana-dkim2-headers (-01).
Rather belatedly this is a response to that
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
At the end of January Dave Crocker posted a review of the then current
"-01" version of draft-gondwana-dkim2-motivation. This document has now
been split into an "-02" and draft-gondwana-dkim2-headers (-01).
Rather belatedly this is a response to that
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
At the end of January Dave Crocker posted a review of the then current
"-01" version of draft-gondwana-dkim2-motivation. This document has now
been split into an "-02" and draft-gondwana-dkim2-headers (-01).
Rather belatedly this is a response to that
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
At the end of January Dave Crocker posted a review of the then current
"-01" version of draft-gondwana-dkim2-motivation. This document has now
been split into an "-02" and draft-gondwana-dkim2-headers (-01).
Rather belatedly this is a response to that
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
At the end of January Dave Crocker posted a review of the then current
"-01" version of draft-gondwana-dkim2-motivation. This document has now
been split into an "-02" and draft-gondwana-dkim2-headers (-01).
Rather belatedly this is a response to that
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
At the end of January Dave Crocker posted a review of the then current
"-01" version of draft-gondwana-dkim2-motivation. This document has now
been split into an "-02" and draft-gondwana-dkim2-headers (-01).
Rather belatedly this is a response to that
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
At the end of January Dave Crocker posted a review of the then current
"-01" version of draft-gondwana-dkim2-motivation. This document has now
been split into an "-02" and draft-gondwana-dkim2-headers (-01).
Rather belatedly this is a response to that
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
At the end of January Dave Crocker posted a review of the then current
"-01" version of draft-gondwana-dkim2-motivation. This document has now
been split into an "-02" and draft-gondwana-dkim2-headers (-01).
Rather belatedly this is a response to that
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
At the end of January Dave Crocker posted a review of the then current
"-01" version of draft-gondwana-dkim2-motivation. This document has now
been split into an "-02" and draft-gondwana-dkim2-headers (-01).
Rather belatedly this is a response to that
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
At the end of January Dave Crocker posted a review of the then current
"-01" version of draft-gondwana-dkim2-motivation. This document has now
been split into an "-02" and draft-gondwana-dkim2-headers (-01).
Rather belatedly this is a response to that
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
At the end of January Dave Crocker posted a review of the then current
"-01" version of draft-gondwana-dkim2-motivation. This document has now
been split into an "-02" and draft-gondwana-dkim2-headers (-01).
Rather belatedly this is a response to that
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
At the end of January Dave Crocker posted a review of the then current
"-01" version of draft-gondwana-dkim2-motivation. This document has now
been split into an "-02" and draft-gondwana-dkim2-headers (-01).
Rather belatedly this is a response to that
It appears that Richard Clayton said:
>>> ++-+
>>> | ds=| Signing key identifier (domain & selector) |
>>
>>So this appears to conflate selector with domain name being signed? Why?
>>
>>How is the domain name be
[As a participant, but hopefully giving broader guidance.]
On 11 Apr 2025, at 14:58, Richard Clayton wrote:
Relays don't change the message. And they typically only add a
Received: header field.
they generally change the destination mailbox as well ...
This is an example of where there doc
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
In message <20250411205917.169acc3d1...@ary.qy>, John Levine
writes
>It appears that Richard Clayton said:
++-+
| ds=| Signing key identifier (domain & select
On 11 Apr 2025, at 13:04, Richard Clayton wrote:
> Let's turn that round ... why did DKIM1 put the selector and the
> associated domain into separate fields ?
>
> If there is a compelling reason for keeping then apart we should take
> note it -- otherwise combining them is of minor assistance in h
According to Richard Clayton :
>-BEGIN PGP SIGNED MESSAGE-
>Hash: SHA1
>
>In message <20250411205917.169acc3d1...@ary.qy>, John Levine
> writes
>
>>It appears that Richard Clayton said:
> ++-+
> | ds=
19 matches
Mail list logo
