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.
Each card starts with one representative test file. Choose a use case, search, or filter to find a specific profile; a card’s variant menu contains its related samples.
36 test families · 113 available files · Page 1 of 2
Delivery
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.
Authentication
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 c
Messages
A multipart/mixed email with a base64-encoded CSV file attachment, for testing attachment detection, decoding, and extraction from an EML message.
Dsn
SAMPLE delivery/DSN-related .eml (bounce-mailbox-full) for mailbox parsers.
Delivery
SAMPLE delivery/DSN-related .eml (calendar-invite-note) for mailbox parsers.
Headers
SAMPLE .eml focusing on auto submitted header behaviour.
Authentication
The failing twin of the all-pass fixture, headers otherwise identical: SPF fail, DKIM fail with a quoted reason property, DMARC fail under p=REJECT. The quoted reason string contains a semicolon-free phrase specifically
Mime
A 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
Mime
The HTML body references a Content-ID that no part in the message provides: the everyday result of a forward that dropped an attachment. A renderer should show the alt text and carry on, not emit a broken external reques
Headers
The ISO-8859-1 Subject again, base64-encoded instead of Q-encoded. Base64 hides the charset entirely, so this is the fixture that catches a decoder guessing the charset from the octets instead of reading the encoded-word
Headers
A To: header listing 24 addresses, folded after every comma. Address-list parsers that unfold and split in the wrong order produce addresses with a leading space or lose the display name of every recipient after the firs
Mime
An 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
Calendar
RFC 822 message with a text/calendar REQUEST attachment, for calendar invite importers.
Mime
A multipart/related message with an HTML body referencing a CID-inline PNG, for email client and MIME parser tests.
Dsn
multipart/report delivery-status SAMPLE with action=delayed for DSN parsers.
Dsn
One multipart/report carrying two per-recipient blocks: a permanent 5.1.1 failure and a temporary 4.4.7 delay for the same original message. Bounce processors that read only the first block suppress a good address, or ke
Threading
A reply carrying the Exchange threading headers (Thread-Topic and a SAMPLE Thread-Index) next to the standard References chain, plus an X-MS header with an empty value. Empty header values are legal and are a common caus
Threading
Simple follow-up SAMPLE message #1 for mailbox threading pads.
