-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

In message <[email protected]>, Bron
Gondwana <[email protected]> writes

>    I had a user report that: bimi-location, bimi-indicator and 
>    bimi-logo-preference should be in the DKIM2 exclusion list.  The 
>    document says that they SHOULD NOT be DKIM signed.  Bah.

I thought BIMI was merely a draft ... and has been for 7 years.

But I see that these headers are intended to be used for communicating
with an MUA, so I assume that the decision to not sign them relates to
not wishing to break a DKIM1 signature by removing earlier copies and
replacing them.

I don't think those considerations would apply to DKIM2

- -- 
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/AwUBavp/MWHfC/FfW545EQJ4FgCfcRD1SmmWZAQuicU3k/V9Ujj/i4oAoLa1
vnoA7tpGaloU/buFaokGN5Mj
=XpW+
-----END PGP SIGNATURE-----
_______________________________________________
Ietf-dkim mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to