-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
In message <[email protected]
il.com>, Emanuel Schorsch <[email protected]> writes
>the current best practices
>recommendations
the current draft of those recommendations ...
> “Under certain circumstances a DKIM2-capable forwarder may choose
> to DKIM2 sign a message with a prior DKIM signature if it can be
> certain that the message was not replayed or introduce backscatter
> using local-policy. Some properties to consider are looking for the
> same anti-replay and backscatter properties described in
> draft-clayton-dkim2-spec except signed with the DKIM signature.
> Typically this only is only apparent for DKIM signed messages at
> origination, meaning when the payload From header is DMARC aligned
> with the DKIM signed domain and the signature is valid.”
>
> Richard, do you agree with that recommendation?
"under certain circumstances" could mean anything ... but as I have said
before I personally see zero value in DKIM2 signing a DKIM1 message
EXCEPT for the case of mailing lists. In neither case is the DKIM2
signature likely to improve deliverability -- but mailing lists may
value the DSNs that may arise, which will come to them in the DKIM2
world
- --
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/AwUBanmN9WHfC/FfW545EQIG2wCdG9AYC69GNTp4OVaG672jYZp203UAoI/G
e0Cn77dfx697wy8HuikiGKnz
=pAPg
-----END PGP SIGNATURE-----
_______________________________________________
Ietf-dkim mailing list -- [email protected]
To unsubscribe send an email to [email protected]
