email parser ignores inner multipart boundary when outer message duplicates it

Open
#69,914 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
backend

Research direction

The issue identifies Python's email component but names no source file, test, or entry point. Start by reproducing the multipart-boundary case and locating the parser code that handles nested multipart messages; done means the inner boundary is honored when it duplicates the outer boundary, with regression coverage.

Written by the indexing model from the issue text.

Description

stdlib topic-email type-bug
BPO 25728
Nosy @warsaw, @bitdancer

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 2015-11-25.00:04:36.589>
labels = ['type-bug', 'expert-email']
title = 'email parser ignores inner multipart boundary when outer message duplicates it'
updated_at = <Date 2015-11-25.14:22:24.477>
user = 'https://bugs.python.org/forest'

bugs.python.org fields:

activity = <Date 2015-11-25.14:22:24.477>
actor = 'r.david.murray'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['email']
creation = <Date 2015-11-25.00:04:36.589>
creator = 'forest'
dependencies = []
files = []
hgrepos = []
issue_num = 25728
keywords = []
message_count = 6.0
messages = ['255309', '255310', '255312', '255313', '255314', '255357']
nosy_count = 3.0
nosy_names = ['barry', 'forest', 'r.david.murray']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'needs patch'
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue25728'
versions = ['Python 2.7', 'Python 3.5', 'Python 3.6']

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.