dkimpy

UTF-8-encoded tag=value pairs

Asked by Gene

I have just started getting DKIM signature headers containing UTF-8 encoded tag/values instead of the usual ascii:

e..g

DKIM-Signature: =?UTF-8?Q?v=3D1;_a=3Drsa-sha256;_c=3Drelaxed/relaxed;_d=3Djpmorgan.com;_h?=
 =?UTF-8?Q?=3Dcontent-transfer-encoding:content-type:date:from:message-id:?=
 =?UTF-8?Q?mime-version:subject:to;_s=3Dd4815;_bh=3Df0W+V/6aYM7VyjJ9iRyfyN?\
...
etc

These are being ignored by dkimpy/dkimpy milter.

I'm aware that RFC 6376 says:

an
      implementation that wished to anticipate future standards would be
      advised not to preclude the use of UTF-8-encoded ([RFC3629]) text
      in tag=value lists.

But I am not aware of any newer RFC speaking to utf-8.

Question:

    Would you consider enhancing dkimpy to recognize these?

thank you.

Question information

Language:
English Edit question
Status:
Answered
For:
dkimpy Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Scott Kitterman (kitterman) said : 		#1

Generally, yes. RFC 8616 has at lease some guidance on this:

https://datatracker.ietf.org/doc/rfc8616/

RFC 8616 support is pretty much next on my list for if I get time to work on feature development. Anything that moves dkimpy in that direction is welcome.

Scott K

Revision history for this message
Gene (gene-arch) said : 		#2

thank you scott.

Will make a point to read 8616.

Can you help with this problem?

Provide an answer of your own, or ask Gene for more information if necessary.

To post a message you must log in.