Issue 9967: encoded_word regular expression in email.header.decode_header() (original) (raw)

Issue9967

Created on 2010-09-28 01:57 by tkikuchi, last changed 2022-04-11 14:57 by admin. This issue is now closed.

Files
File name Uploaded Description Edit
email_header_ecrefix.patch tkikuchi,2010-09-28 01:57 regex fix for encoded_word in email.header.py
Messages (2)
msg117500 - (view) Author: Tokio Kikuchi (tkikuchi) Date: 2010-09-28 01:57
Regular expression ecre for RFC2047 encoded_word in email.header module have bugs: 1. encoded_word should be separated by SPACEs in both leading and trailing ends. Current expression take care only trailing end. 2. encoded_text in the third part of encoded_word should not include literal ? or SPACE. Also, ecre should not match against multiline. The patch includes two test cases for test/test_email.py
msg162236 - (view) Author: R. David Murray (r.david.murray) * (Python committer) Date: 2012-06-03 22:08
Instead of doing this we've opted to follow postel and be generous in what we accept and go ahead and decode even if the leading and/or terminating space is missing (see issue 1079).
History
Date User Action Args
2022-04-11 14:57:07 admin set github: 54176
2012-06-03 22:08:01 r.david.murray set status: open -> closedresolution: rejectedmessages: +
2012-05-16 01:58:16 r.david.murray set assignee: r.david.murray -> components: + email
2011-03-14 03:31:18 r.david.murray set versions: + Python 3.3
2010-12-27 18:28:16 r.david.murray set versions: + Python 3.1, Python 3.2
2010-12-14 18:59:10 r.david.murray set type: behavior
2010-10-23 20:39:21 r.david.murray set assignee: r.david.murray
2010-09-28 07:43:00 ned.deily set nosy: + barry, r.david.murraystage: patch reviewversions: - Python 2.6, Python 2.5
2010-09-28 01:57:44 tkikuchi create