
EML — Thread Depth 4 (Large Headers)
Threaded SAMPLE reply at depth 4 with a long References chain and bulky X-headers.
- File
- EML · Threading
- Use case
- Email parsingConversion testing· Conversion set
Search files, editable visual templates, and live browser targets from one registry-backed directory. Filtered query views stay crawlable for links but are deliberately noindex; the stable taxonomy pages below remain the canonical search surfaces.
Page 4 of 5; 24 results per page.

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

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

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

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

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

A reply carrying In-Reply-To and References headers — for email thread reconstructors.

A mailing-list post carrying three Authentication-Results headers stamped by three different hosts, where DKIM passed upstream and failed at the final hop after the list rewrote the message. Only the topmost header, from the receiving host, may be trusted.

The canonical rich-mail shape written out in full: a mixed container holding a related container holding an alternative pair, plus a CSV attachment at the outer level. A tree walker has to reach depth three to find the HTML body and still report exactly one attachment.

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 first.

Two DKIM-Signature headers for the same message — the RSA/Ed25519 double-signing used during algorithm migrations — with an l= body-length tag on the first. l= means only the first 120 octets are covered, so anything appended afterwards still verifies; both values are SAMPLE placeholders.

A forwarded message carrying a two-instance ARC chain — Seal, Message-Signature and Authentication-Results at i=1 and i=2 — where DKIM broke in transit but ARC records that it passed upstream. Every seal is a visible SAMPLE placeholder, not real cryptography.

An email whose Subject uses RFC 2047 UTF-8 encoded-words (café / crème) — for header decoding tests.

An attachment whose filename uses RFC 2231 UTF-8 encoding (résumé) — for MIME filename decoders.

SAMPLE delivery/DSN-related .eml (bounce-mailbox-full) for mailbox parsers.

SAMPLE delivery/DSN-related .eml (calendar-invite-note) for mailbox parsers.

SAMPLE delivery/DSN-related .eml (dsn-delayed-plain) for mailbox parsers.

SAMPLE delivery/DSN-related .eml (dsn-failed-plain) for mailbox parsers.

SAMPLE delivery/DSN-related .eml (out-of-office) for mailbox parsers.

SAMPLE delivery/DSN-related .eml (receipt-mdn) for mailbox parsers.

SAMPLE .eml focusing on auto submitted header behaviour.

SAMPLE .eml focusing on content language header behaviour.

SAMPLE .eml focusing on dkim signature shape header behaviour.

SAMPLE .eml focusing on list unsubscribe header behaviour.

SAMPLE .eml focusing on priority urgent header behaviour.
We use Google Analytics and show ads via Adsterra. Non-essential cookies and ad scripts run only after you allow the matching categories. See our cookie policy.