Feature Request: Improve MBOX Import Handling for Large Files #109

New Issue

MrUnknownDE · 2026-04-05T16:16:34+02:00

MrUnknownDE commented

2026-04-05 16:16:34 +02:00

Originally created by @coltondick on 11/4/2025

I’d like to suggest some improvements to the MBOX import process, especially for handling large Google Takeout files.

Currently, if a user tries to import a large .mbox file (for example, a 50GB Google Takeout export), the upload fails on the front end.

Proposed Enhancements

Directory Import Option
Add a checkbox to the MBOX ingestion form that switches the import logic to read from disk when selected. This would allow large .mbox files to be processed directly from a mounted directory rather than requiring a front-end upload.
User Mapping Field
Include a new field to specify which user the imported messages belong to (e.g., kevinh@example.com).
In testing, imported emails currently end up in a default mailbox (import@mbox.local), which isn’t ideal for identifying the correct user.

Why This Matters

These changes would make it much easier for power users to import large MBOX archives directly from disk while keeping control over mailbox assignment. It would significantly improve the workflow for users dealing with large-scale email data imports.

*Originally created by @coltondick on 11/4/2025* I’d like to suggest some improvements to the MBOX import process, especially for handling large Google Takeout files. Currently, if a user tries to import a large `.mbox` file (for example, a 50GB Google Takeout export), the upload fails on the front end. ## Proposed Enhancements 1. **Directory Import Option** Add a checkbox to the MBOX ingestion form that switches the import logic to read from disk when selected. This would allow large `.mbox` files to be processed directly from a mounted directory rather than requiring a front-end upload. 2. **User Mapping Field** Include a new field to specify which user the imported messages belong to (e.g., `kevinh@example.com`). In testing, imported emails currently end up in a default mailbox (`import@mbox.local`), which isn’t ideal for identifying the correct user. ## Why This Matters These changes would make it much easier for power users to import large MBOX archives directly from disk while keeping control over mailbox assignment. It would significantly improve the workflow for users dealing with large-scale email data imports.

MrUnknownDE added the enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement labels 2026-04-05 16:16:35 +02:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github/OpenArchiver#109