EML — UTF-8 Filename Attachment
An attachment whose filename uses RFC 2231 UTF-8 encoding (résumé) — for MIME filename decoders.
Content-Type: multipart/mixed; boundary="=_fn_utf8_0001"
MIME-Version: 1.0
From: Docs <docs@meridiansupply.example>
To: Sam Rivera <sam@meridiansupply.example>
Subject: =?utf-8?b?QXR0YWNoZWQgcsOpc3Vtw6k=?=
Date: Sun, 11 Jan 2026 12:00:00 -0800
Message-ID: <fn-utf8@meridiansupply.example>
--=_fn_utf8_0001
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
UGxlYXNlIGZpbmQgdGhlIFNBTVBMRSByw6lzdW3DqSBhdHRhY2hlZC4K
--=_fn_utf8_0001
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename*=utf-8''r%C3%A9sum%C3%A9-sample.txt
QWRhIExvdmVsYWNlIOKAlCBTQU1QTEUgcsOpc3Vtw6kKRXhwZXJpZW5jZTogYW5hbHl0aWNhbCBl
bmdpbmUuCg==
--=_fn_utf8_0001--
Specifications
- Filename Encoding
- RFC 2231 utf-8
- Filename
- résumé-sample.txt
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 — UTF-8 Filename Attachment” is a deterministic Novus Examples fixture for Email parsing, Encoding detection, Internationalization. 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 · 760 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("utf8-filename-attachment.eml", "rb"))
print(msg["subject"], msg["from"])Related files
- emlEML — UTF-8 Encoded SubjectAn email whose Subject uses RFC 2047 UTF-8 encoded-words (café / crème) — for header decoding tests.
- csvBilingual CSV — English→Arabic RTLBilingual EN→AR RTL CSV SAMPLE for spreadsheet CAT and RTL review tools.
- csvBilingual CSV — English→SpanishBilingual EN→ES CSV SAMPLE for spreadsheet-based localization workflows.
- jsonCrowdin-Style Export — FrenchCrowdin-shaped SAMPLE French bilingual export for TMS round-trip tests.
- jsonCrowdin-Style Export — SpanishCrowdin-shaped SAMPLE bilingual export JSON for localization TMS importers.
- csvCSV — Shift-JIS JapaneseA Shift-JIS encoded Japanese CSV — for CJK charset detection and Shift-JIS→UTF-8 conversion in importers.
Generated by generation/email_wave_c.py. Free for any use, no attribution required — license.