EML — multipart/digest With Implicit message/rfc822 Parts
Two complete messages carried in a multipart/digest, neither part declaring a Content-Type. RFC 2046 makes the default message/rfc822 inside a digest instead of the usual text/plain, so a parser that hardcodes the text default renders raw headers as body text.
From: Meridian Ops <ops@meridiansupply.example>
To: Sam Rivera <sam@meridiansupply.example>
Subject: Meridian notices digest, week 7
Date: Thu, 12 Feb 2026 10:10:00 -0800
Message-ID: <p7-digest@brightside.example>
MIME-Version: 1.0
Content-Type: multipart/digest; boundary="=_p7_digest"
--=_p7_digest
From: Meridian Ops <ops@meridiansupply.example>
To: Maya Chen <maya@brightside.example>
Subject: Delivery window changed
Date: Tue, 10 Feb 2026 07:00:00 -0800
Message-ID: <p7-digest-1@brightside.example>
Friday deliveries now arrive before 11:00.
--=_p7_digest
From: Meridian Ops <ops@meridiansupply.example>
To: Maya Chen <maya@brightside.example>
Subject: Backorder cleared
Date: Wed, 11 Feb 2026 07:00:00 -0800
Message-ID: <p7-digest-2@brightside.example>
The nitrile gloves backorder is cleared.
--=_p7_digest--
Specifications
- Wave
- p7
- Seed
- 20260807
- Structure
- multipart/digest
- Enclosed Messages
- 2
- Parts Declare Content Type
- false
- Default Part Type
- message/rfc822 (RFC 2046 s5.1.5)
- Line Endings
- CRLF (RFC 5322)
Testing contract
Expected to pass- Scenario
- Parse a multipart/digest whose parts omit Content-Type and rely on the digest-specific default.
- Expected result
- Both parts are treated as message/rfc822 and split into their own headers and bodies, not shown as text/plain blobs beginning with "From:".
What is a .eml file?
An EML file is a single email message stored in the RFC 822 / MIME format — plain-text headers (From, To, Subject, Date, Message-ID) followed by the body, which may be plain text, HTML, or a multipart structure with alternative bodies and file attachments encoded in base64.
How to use this file
Use an example EML to test email header parsing, MIME decoding, HTML-part handling, attachment extraction, and EML-to-other-format conversion.
How to use this file for testing
“EML — multipart/digest With Implicit message/rfc822 Parts” is a deterministic Novus Examples fixture for Email parsing, Conversion testing. Standards-compliant RFC 822 messages — plain, multipart text+HTML, and with an attachment — plus an MBOX mailbox, for testing header parsing, MIME decoding, attachment extraction, and mailbox splitting.
Documented properties for this file: seed 20260807 · CRLF (RFC 5322) · multipart/digest. Compare results against paired or grouped companions on this page when present (clean↔damaged, searchable↔scanned, or format twins) so scores stay reproducible across runs.
Download the file once, keep the path stable in CI or local scripts, and treat the spec table as the contract: dimensions, seeds, field lists, and roles are intentional. Corrupt or invalid samples are labelled as such — expect parsers to fail loudly rather than silently accept them.
Email fixtures use fixed dates, message IDs, and MIME boundaries so runs are reproducible, and every address is fictional. Test header parsing, MIME decoding, attachment extraction, and EML/MBOX conversion against the documented structure.
Code examples
from email import policy
from email.parser import BytesParser
msg = BytesParser(policy=policy.default).parse(open("nested-digest.eml", "rb"))
print(msg["subject"], msg["from"])Related files
- emlEML — Attachment With No Filename At AllAn attachment with a bare Content-Disposition: attachment and no name in either header. A client has to invent a filename, and the extension it invents decides whether the saved file opens as a spreadsheet or as unknown binary.
- emlEML — Base64: Accented UTF-8 BodyA base64 text/plain message in utf-8 carrying the identical body to the quoted-printable twin beside it. Base64 is opaque to whitespace and line-start characters, so it is the reference side of the pair when a QP decoder is suspect.
- emlEML — Base64: From-Line and Lone DotA base64 text/plain message in utf-8 carrying the identical body to the quoted-printable twin beside it. Base64 is opaque to whitespace and line-start characters, so it is the reference side of the pair when a QP decoder is suspect.
- emlEML — Base64: ISO-8859-1 BodyA base64 text/plain message in iso-8859-1 carrying the identical body to the quoted-printable twin beside it. Base64 is opaque to whitespace and line-start characters, so it is the reference side of the pair when a QP decoder is suspect.
- emlEML — Base64: Soft Line BreaksA base64 text/plain message in utf-8 carrying the identical body to the quoted-printable twin beside it. Base64 is opaque to whitespace and line-start characters, so it is the reference side of the pair when a QP decoder is suspect.
- emlEML — Base64: Trailing WhitespaceA base64 text/plain message in utf-8 carrying the identical body to the quoted-printable twin beside it. Base64 is opaque to whitespace and line-start characters, so it is the reference side of the pair when a QP decoder is suspect.
Generated by generation/email_p7.py. Free for any use, no attribution required — license.