SMTP email policy does not encode non-ASCII characters
Open
Nobody has claimed this yet.
3.7 (EOL)
3.8 (EOL)
stdlib
topic-email
type-bug
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 40157 |
|---|---|
| Nosy | @warsaw, @bitdancer, @aepsil0n |
| Files |
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-04-02.13:52:09.254>
labels = ['3.8', 'type-bug', '3.7', 'expert-email']
title = 'SMTP email policy does not encode non-ASCII characters'
updated_at = <Date 2020-04-02.13:52:09.254>
user = 'https://github.com/aepsil0n'
bugs.python.org fields:
activity = <Date 2020-04-02.13:52:09.254>
actor = 'aepsil0n'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['email']
creation = <Date 2020-04-02.13:52:09.254>
creator = 'aepsil0n'
dependencies = []
files = ['49026']
hgrepos = []
issue_num = 40157
keywords = []
message_count = 1.0
messages = ['365596']
nosy_count = 3.0
nosy_names = ['barry', 'r.david.murray', 'aepsil0n']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue40157'
versions = ['Python 3.6', 'Python 3.7', 'Python 3.8']
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
Start by running the attached minimal.py reproducer and inspect the email handling it exercises. Trace the SMTP policy behavior for non-ASCII characters, then add coverage for the reported case and confirm that the resulting SMTP message encodes those characters correctly.
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
- Mostly clear
- Newbie friendliness
- 35/100