SMTP EmailPolicy not using the correct line length for RCF 2045 encoded data (is 78, should be 76)

Open
#78,206 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
42/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
backend

Research direction

Start by locating Python's SMTP EmailPolicy implementation and the existing email tests, then review how RFC 2045 encoded data is line-wrapped. Add a regression test showing the required 76-character limit and verify that the SMTP policy uses it consistently.

Written by the indexing model from the issue text.

Description

stdlib topic-email type-bug
BPO 34025
Nosy @warsaw, @bitdancer, @maxking, @AldarisPale, @dougthor42

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 2018-07-02.16:18:14.042>
labels = ['type-bug', 'expert-email']
title = 'SMTP EmailPolicy not using the correct line length for RCF 2045 encoded data (is 78, should be 76)'
updated_at = <Date 2021-06-14.18:03:15.960>
user = 'https://github.com/dougthor42'

bugs.python.org fields:

activity = <Date 2021-06-14.18:03:15.960>
actor = 'Douglas Thor'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['email']
creation = <Date 2018-07-02.16:18:14.042>
creator = 'Douglas Thor'
dependencies = []
files = []
hgrepos = []
issue_num = 34025
keywords = []
message_count = 3.0
messages = ['320898', '320905', '324150']
nosy_count = 5.0
nosy_names = ['barry', 'r.david.murray', 'maxking', 'AldarisPale', 'dougthor42']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue34025'
versions = ['Python 3.5']

Dominant language
Python
Stars
77.2k
Forks
36k
Avg merge
1d 9h
Merged PRs (30d)
558

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from python/cpython

All issues in python/cpython

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.