Bug: does not parse multipart/mixed mails with some non-standard boundaries
Open
- Dominant language
- JavaScript
- Stars
- 80
- Forks
- 32
- PR merge metrics
- No merged PRs in 30d
Description
The archiver fails to parse a multipart/mixed email [1]
It looks as though this may be a bug in the Python email parsing, because the email is not detected as multipart, even though there are 3 parts.
[1] http://mail-archives.apache.org/mod_mbox/tomcat-users/200301.mbox/%3CAB3C10C46F698F42B3836BAD91CC0C3F054B21@MARCG-EVS.marcgroup.mail%3E
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the linked multipart/mixed email and trace the archiver's Python email-parsing path to see why the message is not detected as multipart. Confirm the parser recognizes all three parts for this non-standard boundary case; no source file or test is named in the issue.
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
- Mostly clear
- Newbie friendliness
- 35/100