eml1.2 KB

EML — Calendar Invite (REQUEST)

RFC 822 message with a text/calendar REQUEST attachment — for calendar invite importers.

Preview — first 32 lineseml

Content-Type: multipart/mixed; boundary="=_wg_invite_0001"
MIME-Version: 1.0
From: Alex SAMPLE <alex@brightside.example>
To: Sam Rivera <sam@meridiansupply.example>
Subject: Invitation: Novus SAMPLE Planning Sync
Date: Wed, 15 Jan 2026 10:00:00 -0800
Message-ID: <wave-g-invite-001@brightside.example>

--=_wg_invite_0001
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64

WW91J3JlIGludml0ZWQgdG8gYSBTQU1QTEUgcGxhbm5pbmcgc3luYy4K

--=_wg_invite_0001
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="invite.ics"
Content-Type: application/ics; method="REQUEST"

QkVHSU46VkNBTEVOREFSDQpWRVJTSU9OOjIuMA0KUFJPRElEOi0vL05vdnVzIEV4YW1wbGVzLy9T
QU1QTEUvL0VODQpNRVRIT0Q6UkVRVUVTVA0KQkVHSU46VkVWRU5UDQpVSUQ6d2F2ZS1nLW1lZXRp
bmctMDAxQHNhbXBsZS5leGFtcGxlDQpEVFNUQU1QOjIwMjYwMTE1VDE1MDAwMFoNCkRUU1RBUlQ6
MjAyNjAxMjBUMTYwMDAwWg0KRFRFTkQ6MjAyNjAxMjBUMTcwMDAwWg0KU1VNTUFSWTpOb3Z1cyBT
QU1QTEUgUGxhbm5pbmcgU3luYw0KT1JHQU5JWkVSO0NOPUFsZXggU0FNUExFOm1haWx0bzphbGV4
QGJyaWdodHNpZGUuZXhhbXBsZQ0KQVRURU5ERUU7Q049U2FtIFJpdmVyYTtSU1ZQPVRSVUU6bWFp
bHRvOnNhbUBtZXJpZGlhbnN1cHBseS5leGFtcGxlDQpTVEFUVVM6Q09ORklSTUVEDQpTRVFVRU5D
RTowDQpFTkQ6VkVWRU5UDQpFTkQ6VkNBTEVOREFSDQo=

--=_wg_invite_0001--

Specifications

Method: REQUEST
Uid: wave-g-meeting-001@sample.example
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 — Calendar Invite (REQUEST)” 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 · 1,256 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("invite-request.eml", "rb"))
print(msg["subject"], msg["from"])