Message326996
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 implement this you need to add a new TokenList class to _header_value_parser, say DKIMHeaderValue, with the class attribute 'as_ew_allowed' set to False.
Do you have a BNF description of the DKIM header? I could probably sketch the implementation of the DKIM header value parser from that.
Then you create a header in headerregistry that uses that parser as its value_parser. |
|
Date |
User |
Action |
Args |
2018-10-03 17:51:47 | r.david.murray | set | recipients:
+ r.david.murray, barry, bryced |
2018-10-03 17:51:47 | r.david.murray | set | messageid: <1538589107.38.0.545547206417.issue34881@psf.upfronthosting.co.za> |
2018-10-03 17:51:47 | r.david.murray | link | issue34881 messages |
2018-10-03 17:51:47 | r.david.murray | create | |
|