EML — Threaded References Headers
A reply carrying In-Reply-To and References headers — for email thread reconstructors.
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
From: Ada <ada@meridiansupply.example>
To: Ben <ben@meridiansupply.example>
Subject: Re: SAMPLE project kickoff
Date: Sat, 10 Jan 2026 16:00:00 -0800
Message-ID: <thread-3@meridiansupply.example>
In-Reply-To: <thread-2@meridiansupply.example>
References: <thread-1@meridiansupply.example>
<thread-2@meridiansupply.example>
UmU6IFNBTVBMRSB0aHJlYWQg4oCUIHRoaXJkIHJlcGx5Lgo=
Specifications
- In Reply To
- present
- References
- two Message-IDs
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 — Threaded References Headers” 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: EML · 468 bytes. 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("threaded-reply.eml", "rb"))
print(msg["subject"], msg["from"])Related files
- emlBounce / Non-Delivery Report (EML)A bounce / non-delivery report (NDR) — a multipart/report message with a human-readable notice, a message/delivery-status part, and the original headers — for testing bounce parsing and delivery-status extraction.
- emlEmail with Attachment (EML)A multipart/mixed email with a base64-encoded CSV file attachment — for testing attachment detection, decoding, and extraction from an EML message.
- emlEML — Calendar Invite (REQUEST)RFC 822 message with a text/calendar REQUEST attachment — for calendar invite importers.
- emlEML — Calendar Invite Cancel (CANCEL)Cancel twin for the SAMPLE calendar invite — same UID, SEQUENCE bumped, METHOD=CANCEL.
- emlEML — CID Inline ImageA multipart/related message with an HTML body referencing a CID-inline PNG — for email client and MIME parser tests.
- emlEML — DSN Delayed SAMPLEmultipart/report delivery-status SAMPLE with action=delayed for DSN parsers.
Generated by generation/email_wave_c.py. Free for any use, no attribution required — license.