encoded-word abused for header line folding causes RFC 2047 violation
Open
Nobody has claimed this yet.
3.7 (EOL)
topic-email
type-bug
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 41553 |
|---|---|
| Nosy | @warsaw, @bitdancer, @websurfer5 |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
assignee = None
closed_at = None
created_at = <Date 2020-08-14.11:53:18.338>
labels = ['type-bug', '3.7', 'expert-email']
title = 'encoded-word abused for header line folding causes RFC 2047 violation'
updated_at = <Date 2020-08-18.11:57:09.578>
user = 'https://bugs.python.org/equaeghe'
bugs.python.org fields:
activity = <Date 2020-08-18.11:57:09.578>
actor = 'Mika_Hawkins'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['email']
creation = <Date 2020-08-14.11:53:18.338>
creator = 'equaeghe'
dependencies = []
files = []
hgrepos = []
issue_num = 41553
keywords = []
message_count = 6.0
messages = ['375397', '375409', '375411', '375434', '375566', '375612']
nosy_count = 5.0
nosy_names = ['barry', 'r.david.murray', 'equaeghe', 'Jeffrey.Kintscher', 'Mika_Hawkins']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue41553'
versions = ['Python 3.7']
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue concerns Python's email component and RFC 2047 header folding, but the payload names no source files, tests, or entry points. Start by locating the email header encoding and folding implementation and its existing tests; done means the behavior no longer violates RFC 2047 and the relevant regression coverage passes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100