The short answer
- MBOX is a family of email archive formats that stores messages sequentially in one file, usually for one mail folder rather than an account’s entire folder hierarchy.
- Keep the original and work with a copy. On Windows or Mac, choose an email client whose import documentation supports the source MBOX variant, then import the copy. On a phone, first check whether the app supports that variant; if support is unclear, use a compatible desktop client. A plain-text tool can inspect message text, but this is not equivalent to importing messages or extracting attachments.
- RFC 4155 describes MBOX as passive data that generally introduces no unique or new security threats. The low risk rating concerns the container, not the trustworthiness of its messages or attachments. MBOX has no built-in encryption, and sharing it can expose email information. Neither the extension nor a “From ” prefix proves safety or validity.
MBOX files: open, import and convert email archives
Messages usually start with a separator line beginning with “From ” and containing sender and time information. Attachments can remain in their MIME representation inside the archive. The registered media type is application/mbox. MBOXO, MBOXRD, MBOXCL and MBOXCL2 differ in how they identify message boundaries; readers are not necessarily interchangeable.
Before converting, confirm that the reader supports the source variant and that the exporter supports your intended output. If you need EML, verify that export capability explicitly. Conversion cannot be assumed lossless: variant mismatches can damage messages or prevent recovery of later mail. Compare message counts, text and attachments against the original. When sending an MBOX as an email attachment, use appropriate transfer encoding such as Base64 or Quoted-Printable to avoid separator collisions if it is stored inside another MBOX.
How to open it
Keep the original and work with a copy. On Windows or Mac, choose an email client whose import documentation supports the source MBOX variant, then import the copy. On a phone, first check whether the app supports that variant; if support is unclear, use a compatible desktop client. A plain-text tool can inspect message text, but this is not equivalent to importing messages or extracting attachments.
Keep the original and work with a copy. On Windows or Mac, choose an email client whose import documentation supports the source MBOX variant, then import the copy. On a phone, first check whether the app supports that variant; if support is unclear, use a compatible desktop client. A plain-text tool can inspect message text, but this is not equivalent to importing messages or extracting attachments.
Before converting, confirm that the reader supports the source variant and that the exporter supports your intended output. If you need EML, verify that export capability explicitly. Conversion cannot be assumed lossless: variant mismatches can damage messages or prevent recovery of later mail. Compare message counts, text and attachments against the original. When sending an MBOX as an email attachment, use appropriate transfer encoding such as Base64 or Quoted-Printable to avoid separator collisions if it is stored inside another MBOX.
File safety
RFC 4155 describes MBOX as passive data that generally introduces no unique or new security threats. The low risk rating concerns the container, not the trustworthiness of its messages or attachments. MBOX has no built-in encryption, and sharing it can expose email information. Neither the extension nor a “From ” prefix proves safety or validity.
An unknown sender, a name ending in two extensions, or contents that do not match the extension — check before you open it.
Converting it
Before converting, confirm that the reader supports the source variant and that the exporter supports your intended output. If you need EML, verify that export capability explicitly. Conversion cannot be assumed lossless: variant mismatches can damage messages or prevent recovery of later mail. Compare message counts, text and attachments against the original. When sending an MBOX as an email attachment, use appropriate transfer encoding such as Base64 or Quoted-Printable to avoid separator collisions if it is stored inside another MBOX.
Convert a copy, never the original, then compare quality, metadata, and layout against what you started with.
Common questions
What is an MBOX file used for?
An MBOX file stores a sequence of email messages, usually corresponding to one mail folder. It does not normally preserve an account’s entire folder hierarchy in that single file.
How do I open an MBOX email archive?
Use an email client that explicitly supports importing the source MBOX variant. Import a copy and retain the original; a plain-text tool can also inspect the message text.
How do I import MBOX on Windows?
Choose a Windows email client with documented import support for your MBOX variant, then import a copy. Check messages and attachments before relying on the imported archive.
How do I open MBOX on Mac?
Use a Mac email client whose import documentation covers the source variant. Keep the original, import a copy and check the resulting messages.
How do I open MBOX on a phone?
Check whether your phone’s email app supports importing the specific MBOX variant. If support is unclear, use a compatible desktop client; the .mbox extension alone does not establish app compatibility.
Why are MBOX messages missing after import?
The reader may be interpreting a different MBOX variant. Differences in message boundaries, escaping of body lines beginning with “From ”, encoding or line endings can cause parsing problems. Return to the original and confirm variant support before trying again; recovery is not guaranteed.
Should I choose MBOXO or MBOXRD for an MBOX archive?
Choose the variant explicitly supported by both the exporting and importing tools. MBOXO and MBOXRD differ in handling body lines beginning with “From ”, so they should not be treated as interchangeable.
Can I convert MBOX to EML without losing email content?
Do not assume lossless conversion. First confirm support for the source MBOX variant and EML export, then compare message counts, text and attachments with the original.
Is an MBOX file received by email safe to open?
MBOX is a passive container, but that does not certify its messages or attachments as safe. Consider the sender and contents; the filename and “From ” prefix are not safety guarantees.
Does an MBOX archive support built-in encryption?
No. MBOX has no built-in encryption option. Sharing the archive can expose email information, so consider the sensitivity of its contents before sending it.
How do I extract attachments from MBOX?
Attachments can be stored in their MIME representation within the messages. Use a reader compatible with the source variant and confirm that it offers attachment saving; viewing the raw text alone does not extract them.
Does a “From ” prefix prove that an MBOX file is valid?
No. It is a common separator feature, but it does not establish completeness, compatibility with a particular variant, or the trustworthiness of the contents.
Related formats
Sources
RFC 4155: The application/mbox Media Type · RFC Editor；MBOX 媒体类型注册及默认交换格式文档
MBOX Email Format · 美国国会图书馆；数字格式保存说明