EML Header — Thread Topic
SAMPLE .eml focusing on thread topic header behaviour.
From: Alex SAMPLE <alex@brightside.example>
To: Sam Rivera <sam@meridiansupply.example>
Subject: Re: Project SAMPLE kickoff
Date: Wed, 22 Jul 2026 09:20:00 -0400
Message-ID: <wi-thread-topic@brightside.example>
In-Reply-To: <kickoff@brightside.example>
References: <kickoff@brightside.example>
Thread-Topic: Project SAMPLE kickoff
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Threading SAMPLE body.
Specifications
- Role
- header-variant
- Wave
- I
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 Header — Thread Topic” is a deterministic Novus Examples fixture for Email parsing. 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: header-variant. 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("thread-topic.eml", "rb"))
print(msg["subject"], msg["from"])Related files
- emlEML — Threaded References HeadersA reply carrying In-Reply-To and References headers — for email thread reconstructors.
- emlEML — UTF-8 Encoded SubjectAn email whose Subject uses RFC 2047 UTF-8 encoded-words (café / crème) — for header decoding tests.
- 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.
- emlDKIM / SPF Annotated Email (EML)An email annotated with DKIM-Signature, Received-SPF, and Authentication-Results headers (all reporting pass) — for testing email-authentication header parsing. The DKIM signature value is a sample placeholder, not real cryptography.
- 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.
Generated by generation/pad_wave_i.py. Free for any use, no attribution required — license.