smtplib.SMTP should reset internal 'helo' and 'ehlo' state within 'connect()'
Open
Nobody has claimed this yet.
3.8 (EOL)
stdlib
topic-email
type-bug
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 558
Description
| BPO | 41470 |
|---|---|
| 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-04.09:39:24.082>
labels = ['type-bug', '3.8', 'expert-email']
title = "smtplib.SMTP should reset internal 'helo' and 'ehlo' state within 'connect()'"
updated_at = <Date 2020-08-05.23:25:36.525>
user = 'https://bugs.python.org/Dadeos'
bugs.python.org fields:
activity = <Date 2020-08-05.23:25:36.525>
actor = 'Jeffrey.Kintscher'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['email']
creation = <Date 2020-08-04.09:39:24.082>
creator = 'Dadeos'
dependencies = []
files = []
hgrepos = []
issue_num = 41470
keywords = []
message_count = 1.0
messages = ['374798']
nosy_count = 4.0
nosy_names = ['barry', 'r.david.murray', 'Jeffrey.Kintscher', 'Dadeos']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue41470'
versions = ['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 at smtplib.SMTP.connect() and trace how the internal helo and ehlo state is managed. Done means reconnecting through connect() resets both states as requested, with regression coverage for the reported behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100