smtplib is glitchy after receive server code 500
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 | 42498 |
|---|---|
| Nosy | @warsaw, @bitdancer, @pepoluan |
| 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-11-29.05:30:35.881>
labels = ['3.7', 'expert-email', 'type-crash']
title = 'smtplib is glitchy after receive server code 500'
updated_at = <Date 2021-01-05.19:01:17.663>
user = 'https://bugs.python.org/izomiac'
bugs.python.org fields:
activity = <Date 2021-01-05.19:01:17.663>
actor = 'izomiac'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['email']
creation = <Date 2020-11-29.05:30:35.881>
creator = 'izomiac'
dependencies = []
files = ['49634']
hgrepos = []
issue_num = 42498
keywords = []
message_count = 3.0
messages = ['382038', '384373', '384426']
nosy_count = 4.0
nosy_names = ['barry', 'r.david.murray', 'izomiac', 'pepoluan']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'crash'
url = 'https://bugs.python.org/issue42498'
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
Start with the attached debug output.txt and trace the smtplib email path involved after the server returns code 500. Determine the expected behavior from the connection logs, then verify the fix against that failure scenario and add coverage if the relevant test location can be identified.
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
- 28/100