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 header folded incorrectly
Type: behavior Stage: resolved
Components: email Versions: Python 3.7
Status: closed Resolution: fixed
Dependencies: Superseder:
Assigned To: Nosy List: Jeffrey.Kintscher, Jonathan Horn, barry, iritkatriel, miss-islington, r.david.murray
Priority: normal Keywords: patch

Created on 2019-04-03 23:15 by Jonathan Horn, last changed 2022-04-11 14:59 by admin. This issue is now closed.

File name Uploaded Description Edit Jeffrey.Kintscher, 2019-05-27 10:43 UTF-8 header encoding test cases
Pull Requests
URL Status Linked Edit
PR 13608 merged Jeffrey.Kintscher, 2019-05-28 02:33
PR 13610 closed Jeffrey.Kintscher, 2019-05-28 03:38
PR 13909 merged maxking, 2019-06-08 07:50
PR 13910 merged maxking, 2019-06-08 07:50
Messages (10)
msg339419 - (view) Author: Jonathan Horn (Jonathan Horn) Date: 2019-04-03 23:15
I encountered a problem with replacing the 'Subject' header of an email. After serializing it again, the utf8 encoding was wrong. It seems to be occurring when folding the internal header objects.

>> email.policy.default.fold_binary('Subject', email.policy.default.header_store_parse('Subject', 'Hello Wörld! Hello Wörld! Hello Wörld! Hello Wörld!Hello Wörld!')[1])
Expected output: b'Subject: Hello =?utf-8?q?W=C3=B6rld!_Hello_W=C3=B6rld!_Hello_W=C3=B6rld!?=\n Hello =?utf-8?q?W=C3=B6rld!Hello_W=C3=B6rld!?=\n' (or similar)
Actual output: b'Subject: Hello =?utf-8?q?W=C3=B6rld!_Hello_W=C3=B6rld!_Hello_W=C3=B6rld!?=\n Hello =?utf-8?=?utf-8?q?q=3FW=3DC3=3DB6rld!Hello=3F=3D_W=C3=B6rld!?=\n'

I'm running Python 3.7.3 on Arch Linux using Linux 5.0.
msg343267 - (view) Author: R. David Murray (r.david.murray) * (Python committer) Date: 2019-05-23 01:34
Can you demonstrate the problem with an actual email object?  header_store_parse is not meant to be called directly.
msg343268 - (view) Author: R. David Murray (r.david.murray) * (Python committer) Date: 2019-05-23 01:39
Nevermind, I was testing with the wrong version of python.  This bug was introduced somewhere after 3.4 :(

>>> from email.message import EmailMessage
>>> m = EmailMessage()
>>> m['Subject'] = 'Hello Wörld! Hello Wörld! Hello Wörld! Hello Wörld!Hello Wörld!'
>>> bytes(m)
b'Subject: Hello =?utf-8?q?W=C3=B6rld!_Hello_W=C3=B6rld!_Hello_W=C3=B6rld!?=\n Hello =?utf-8?=?utf-8?q?q=3FW=3DC3=3DB6rld!Hello=3F=3D_W=C3=B6rld!?=\n\n'
msg343606 - (view) Author: Jeffrey Kintscher (Jeffrey.Kintscher) * Date: 2019-05-27 03:43
To aid with debugging the code, the Subject line can be simplified:

>>> from email.message import EmailMessage
>>> m = EmailMessage()
>>> m['Subject'] = 'Hello =?utf-8?q?W=C3=B6rld!_Hello_W=C3=B6rld!_Hello_W=C3=B6rld!?= Hello Wörld!Hello Wörld!'
>>> print(bytes(m))
b'Subject: Hello =?utf-8?q?W=C3=B6rld!_Hello_W=C3=B6rld!_Hello_W=C3=B6rld!?=\n Hello =?utf-8?=?utf-8?q?q=3FW=3DC3=3DB6rld!Hello=3F=3D_W=C3=B6rld!?=\n\n'
msg343612 - (view) Author: Jeffrey Kintscher (Jeffrey.Kintscher) * Date: 2019-05-27 10:43
I uploaded a test script with some test cases:

The failure mode occurs when

1. line folding occurs
2. the first folded line has two or more words with UTF-8 characters
3. subsequent lines contain a word with UTF-8 characters located at a different offset than the last encoded substring in the first line

For example, the first folded and encoded line of 'Hello Wörld! Hello Wörld! Hello Wörld! Hello Wörld!Hello Wörld!' is

b'Subject: Hello =?utf-8?q?W=C3=B6rld!_Hello_W=C3=B6rld!_Hello_W=C3=B6rld!?='

and the second line should be

b' Hello =?utf-8?q?W=C3=B6rld!Hello_W=C3=B6rld!?='

but instead, it is

b' Hello =?utf-8?=?utf-8?q?q=3FW=3DC3=3DB6rld!Hello=3F=3D_W=C3=B6rld!?='

The function at fault is _refold_parse_tree() in Lib/email/ In the first line, it encodes the first UTF-8 word and saves the starting offset in the output string (15). When it encounters the second UTF-8 word, it re-encodes the entire string starting at the saved offset. This is to help reduce the bloat added by multiple '=?utf-8?q?' start-of-encoding tokens. When it encodes the first UTF-8 word on the second line, it tries to store it at the saved offset into the second line output string, but that is past the end of the string so it just gets appended. When it encounter the second UTF-8 word in the second line, it re-encodes the entire second-line string starting at the saved offset (15), which is in the middle of the first encoded UTF-8 string.

The failure mode is not triggered if there is at most one UTF-8 word in each folded line. It also is not triggered when folding occurs in the middle of a word instead of at whitespace because the code follows a different path.

The solution is to set the saved starting offset to None when starting a new folded line when the fold-point is whitespace.

I will submit a pull request soon with a fix.
msg343730 - (view) Author: Jeffrey Kintscher (Jeffrey.Kintscher) * Date: 2019-05-28 04:49
The pull request has been submitted with both the code fix and tests.
msg344863 - (view) Author: Barry A. Warsaw (barry) * (Python committer) Date: 2019-06-06 19:53
New changeset f6713e84afc5addcfa8477dbdf2c027787f711c0 by Barry Warsaw (websurfer5) in branch 'master':
bpo-36520: Email header folded incorrectly (#13608)
msg345287 - (view) Author: miss-islington (miss-islington) Date: 2019-06-11 23:27
New changeset 0745cc66db3acbe7951073071cf063db6337dd10 by Miss Islington (bot) (Abhilash Raj) in branch '3.7':
[3.7] bpo-36520: Email header folded incorrectly (GH-13608) (GH-13910)
msg345288 - (view) Author: miss-islington (miss-islington) Date: 2019-06-11 23:28
New changeset 36eea7af48ca0a1c96b78c82bf95bbd29d2332da by Miss Islington (bot) (Abhilash Raj) in branch '3.8':
[3.8] bpo-36520: Email header folded incorrectly (GH-13608) (GH-13909)
msg378380 - (view) Author: Irit Katriel (iritkatriel) * (Python committer) Date: 2020-10-10 10:37
This seems complete, can it be closed?
Date User Action Args
2022-04-11 14:59:13adminsetgithub: 80701
2020-11-20 15:09:53iritkatrielsetstatus: open -> closed
resolution: fixed
stage: patch review -> resolved
2020-10-10 10:37:54iritkatrielsetnosy: + iritkatriel
messages: + msg378380
2019-06-11 23:28:18miss-islingtonsetmessages: + msg345288
2019-06-11 23:27:16miss-islingtonsetnosy: + miss-islington
messages: + msg345287
2019-06-08 07:50:36maxkingsetpull_requests: + pull_request13783
2019-06-08 07:50:27maxkingsetpull_requests: + pull_request13782
2019-06-06 19:53:49barrysetmessages: + msg344863
2019-05-28 04:49:18Jeffrey.Kintschersetmessages: + msg343730
2019-05-28 03:38:14Jeffrey.Kintschersetpull_requests: + pull_request13515
2019-05-28 02:33:18Jeffrey.Kintschersetkeywords: + patch
stage: patch review
pull_requests: + pull_request13514
2019-05-27 10:43:16Jeffrey.Kintschersetfiles: +

messages: + msg343612
2019-05-27 03:43:45Jeffrey.Kintschersetmessages: + msg343606
2019-05-23 01:39:57r.david.murraysetmessages: + msg343268
2019-05-23 01:34:59r.david.murraysetmessages: + msg343267
2019-05-22 09:16:10Jeffrey.Kintschersetnosy: + Jeffrey.Kintscher
2019-04-03 23:15:00Jonathan Horncreate