Enh: add support for mboxrd format
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- javascript
- Domain
- backend
Research direction
Start by tracing the code that reads mbox files and generates mbox download files, since the issue identifies both paths as using mboxo. Compare their current escaping and unescaping behavior with the mboxrd rules described here; done means mboxrd input and output are supported while existing mboxo behavior remains available.
Written by the indexing model from the issue text.
Description
Body lines in mbox files must not start with the characters 'From ' as the string identifies the start of the next message.
Unfortunately there is no single standard for how such lines are handled.
The mboxo format changes 'From ' to '>From '; this is ambiguous when attempting to regenerate the original email.
The mboxrd format additionally changes '>From ' to '>>From ' etc, which is reversible.
Apache HTTPD mod_mbox currently uses mboxo (as far as I am aware).
The ASF mbox-vm archiver uses mboxrd.
PonyMail currently uses mboxo for generating mbox downloadfiles and defaults to reading mbox files as mboxo.
Whilst this is self-consistent, it is not ideal.
The code should allow for mboxrd support.
- Dominant language
- JavaScript
- Stars
- 80
- Forks
- 32
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from apache/ponymail
-
Difficulty 3/5 1-2 days Newbie friendliness 38/100
-
Difficulty 3/5 1-2 days Newbie friendliness 42/100
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
-
Difficulty 4/5 3-5 days Newbie friendliness 20/100
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 65/100
-
[BUG] Tools returned by input processors get an empty context.agent.agentIdMay be free again A pull request for this issue was closed without being merged. Open@mastra/core effort:low impact:medium status: auto-triaged Tools
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
mastra-ai/mastra#26794 · 3 comments ·
Maintainers usually reply within 1 day
-
release:v5.34
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
Jason-Vaughan/TangleClaw#2365 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
enhancement
Difficulty 1/5 1-3 hours Newbie friendliness 85/100
holepunchto/hrpc-test#28 ·