Message398101
Try parsing an example such as this through the Python email library:
Content-Type: message/global
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; =
charset=3D”us-ascii”
Hello, World!
You will find that the valid quoted-printable content is visited but not decoded prior to parsing; it is parsed as-is and treated as a bad message: the charset in the “text/plain” Content-Type improperly parsed, for example. I have a draft pull request for this, which might be easier to understand. Let me know if you need further clarification. |
|
Date |
User |
Action |
Args |
2021-07-23 21:45:36 | f18a14c09s | set | recipients:
+ f18a14c09s, barry, terry.reedy, r.david.murray, python-dev |
2021-07-23 21:45:36 | f18a14c09s | set | messageid: <1627076736.19.0.878812888106.issue44660@roundup.psfhosted.org> |
2021-07-23 21:45:36 | f18a14c09s | link | issue44660 messages |
2021-07-23 21:45:36 | f18a14c09s | create | |
|