This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Title: Email headers do not properly decode to unicode.
Type: behavior Stage: resolved
Components: Documentation, email Versions: Python 3.3, Python 3.4
Status: closed Resolution: fixed
Dependencies: Superseder:
Assigned To: docs@python Nosy List: Tim.Rawlinson, barry, docs@python, ezio.melotti, python-dev, r.david.murray
Priority: normal Keywords:

Created on 2013-05-23 11:57 by Tim.Rawlinson, last changed 2022-04-11 14:57 by admin. This issue is now closed.

Messages (4)
msg189862 - (view) Author: Tim Rawlinson (Tim.Rawlinson) Date: 2013-05-23 11:57
In Python 3.3 decoding of headers to unicode is supposed to be automatic but fails in several cases, including one shown as successful in the documentation:

   >>> msg = message_from_string('Subject: =?utf-8?q?=C3=89ric?=\n\n', policy=default)
   >>> msg['Subject']

   >>> msg = message_from_string('To: =?utf-8?q?=C3=89ric <>\n\n', policy=default)
   >>> msg['To']
   '=?utf-8?q?=C3=89ric?= <>'

Although the following works:

   >>> msg = message_from_string('Subject: =?utf-8?q?Eric?=\n\n', policy=default)
   >>> msg['Subject']

Though this does not:

   >>> msg = message_from_string('To: =?utf-8?q?Eric?= <>\n\n', policy=default)
   >>> msg['To']
   '=?utf-8?q?Eric?= <>'

And just to prove some things are working as they should:

    >>> msg = message_from_string("Subject: =?gb2312?b?1eLKx9bQzsSy4srUo6E=?=\n\n", policy=default)
    >>> msg['Subject']
msg192894 - (view) Author: Roundup Robot (python-dev) (Python triager) Date: 2013-07-11 19:59
New changeset 4acb822f4c43 by R David Murray in branch '3.3':
#18044: Fix parsing of encoded words of the form =?utf8?q?=XX...?=

New changeset 32c6cfffbddd by R David Murray in branch 'default':
Merge: #18044: Fix parsing of encoded words of the form =?utf8?q?=XX...?=
msg192895 - (view) Author: R. David Murray (r.david.murray) * (Python committer) Date: 2013-07-11 20:06
This is actually two separate bugs, both a bit embarrassing.  The first one (that I just fixed) is that when parsing an encoded word I was only checking for decimal digits after an '=' (instead of the correct hex digits) when trying to do robust detection of encoded word limits.  

The second (the address one) is due to the fact that somewhere between stopping my full time work on the email project and actually committing the code, I lost track of the fact that I never implemented encoded word parsing for anything other than unstructured headers.  The infrastructure is there, I just need to write tests and hook it up.  

I'm going to open a separate issue for that.
msg192899 - (view) Author: R. David Murray (r.david.murray) * (Python committer) Date: 2013-07-11 20:11
The issue for the second bug is issue 18431.
Date User Action Args
2022-04-11 14:57:45adminsetgithub: 62244
2013-07-11 20:11:20r.david.murraysetmessages: + msg192899
2013-07-11 20:06:03r.david.murraysetstatus: open -> closed
versions: + Python 3.4
messages: + msg192895

resolution: fixed
stage: resolved
2013-07-11 19:59:04python-devsetnosy: + python-dev
messages: + msg192894
2013-05-26 13:41:13ezio.melottisetnosy: + ezio.melotti
2013-05-23 11:57:36Tim.Rawlinsoncreate