python / python/cpython

mailbox.MH crashes on certain Claws Mail .mh_sequences files

Open
#72,659 7 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

3.7 (EOL) stdlib topic-email type-feature
Dominant language
Python
Stars
77.2k
Forks
36k
PR merge metrics
PR metrics pending

Description

BPO 28473
Nosy @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 2016-10-18.22:39:26.549>
labels = ['3.7', 'type-feature', 'library']
title = 'mailbox.MH crashes on certain Claws Mail .mh_sequences files'
updated_at = <Date 2016-10-29.18:47:04.178>
user = 'https://bugs.python.org/garrettzilla'

bugs.python.org fields:

activity = <Date 2016-10-29.18:47:04.178>
actor = 'r.david.murray'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2016-10-18.22:39:26.549>
creator = 'garrettzilla'
dependencies = []
files = []
hgrepos = []
issue_num = 28473
keywords = []
message_count = 7.0
messages = ['278945', '278954', '278955', '278972', '279683', '279684', '279693']
nosy_count = 2.0
nosy_names = ['r.david.murray', 'garrettzilla']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue28473'
versions = ['Python 3.6', 'Python 3.7']

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.

Research direction

Start at the Python mailbox.MH entry point and read the linked BPO issue 28473 for the missing reproduction details about Claws Mail .mh_sequences files. Reproduce the crash, identify the affected input, and verify that the behavior is covered by a regression test without breaking existing mailbox parsing.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.