eml906 B

EML — DSN Relayed SAMPLE

multipart/report delivery-status SAMPLE with action=relayed for DSN parsers.

Preview — first 32 lineseml

From: Mailer-Daemon <postmaster@mail.sample.example>
To: Alex SAMPLE <alex@brightside.example>
Subject: Delivery Status Notification (relayed) SAMPLE
Date: Tue, 24 Jan 2026 08:00:00 -0800
Message-ID: <dsn-04@mail.sample.example>
MIME-Version: 1.0
Content-Type: multipart/report; report-type=delivery-status; boundary="=_wg_dsn_04"

--=_wg_dsn_04
Content-Type: text/plain; charset=utf-8

Your message to sam@meridiansupply.example: relayed.
--=_wg_dsn_04
Content-Type: message/delivery-status

Reporting-MTA: dns; mail.sample.example

Final-Recipient: rfc822; sam@meridiansupply.example
Action: relayed
Status: 2.0.0
Diagnostic-Code: smtp; SAMPLE diagnostic
--=_wg_dsn_04
Content-Type: message/rfc822

From: Alex SAMPLE <alex@brightside.example>
To: Sam Rivera <sam@meridiansupply.example>
Subject: Original SAMPLE
Message-ID: <orig-dsn-04@brightside.example>

Original SAMPLE message body.
--=_wg_dsn_04--

Specifications

Report Type: delivery-status
Action: relayed
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 — DSN Relayed SAMPLE” 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 · 906 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("dsn-relayed.eml", "rb"))
print(msg["subject"], msg["from"])