eml782 B

EML — Thread Depth 1 (Large Headers)

Threaded SAMPLE reply at depth 1 with a long References chain and bulky X-headers.

Preview — first 18 lineseml

Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
From: User1 SAMPLE <u1@brightside.example>
To: Sam Rivera <sam@meridiansupply.example>
Subject: Re: Deep thread SAMPLE (1)
Date: Mon, 11 Jan 2026 12:00:00 -0800
Message-ID: <thread-depth-01@brightside.example>
In-Reply-To: <thread-root@brightside.example>
References: <thread-root@brightside.example>
X-Novus-Sample-0: value-1-0-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
X-Novus-Sample-1: value-1-1-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
X-Novus-Sample-2: value-1-2-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
X-Novus-Sample-3: value-1-3-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
X-Novus-Sample-4: value-1-4-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

VGhyZWFkIGRlcHRoIFNBTVBMRSByZXBseSAjMS4K

Specifications

Depth: 1
References Count: 1
Custom Headers: 5
Wave: G

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 — Thread Depth 1 (Large 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 · 782 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("depth-01.eml", "rb"))
print(msg["subject"], msg["from"])