Abhilash Raj added the comment:
Just for reference DKIM-Signature header is defined in RFC 6376 and the BNF
description for the header is mentioned here
(https://tools.ietf.org/html/rfc6376#section-3.5).
It is a bit long so I am not copy-pasting it here.
I might take a stab at writing a val
R. David Murray added the comment:
You could also play with just making a parser that is a simplified version of
get_unstructured, producing amaybe call it
ASCIIOnlyUnstructuredTokenList...that would have as_ew_allowed set to False.
That might not produce optimal results, but it would b
R. David Murray added the comment:
See also issue 34277 for a previous discussion.
I thought I had included a header-level toggle for encoded words, but that
doesn't actually make sense, since by default a header value is treated as
unstructured (which means encoded words are allowed).
To i
New submission from Bryce Drennan :
Since Python 3.6.4 folding of unstructured headers uses the encoded words
syntax even if there are no special characters.
This makes DKIM-Signature headers that are unreadable to google's gmail
servers. It may be that encoded-words are not valid in this h
