EML — Calendar Invite Cancel (CANCEL)
Cancel twin for the SAMPLE calendar invite — same UID, SEQUENCE bumped, METHOD=CANCEL.
Content-Type: multipart/mixed; boundary="=_wg_cancel_0001"
MIME-Version: 1.0
From: Alex SAMPLE <alex@brightside.example>
To: Sam Rivera <sam@meridiansupply.example>
Subject: Cancelled: Novus SAMPLE Planning Sync
Date: Thu, 16 Jan 2026 02:00:00 -0800
Message-ID: <wave-g-cancel-001@brightside.example>
In-Reply-To: <wave-g-invite-001@brightside.example>
References: <wave-g-invite-001@brightside.example>
--=_wg_cancel_0001
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
VGhlIFNBTVBMRSBwbGFubmluZyBzeW5jIGhhcyBiZWVuIGNhbmNlbGxlZC4K
--=_wg_cancel_0001
Content-Type: application/ics
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="cancel.ics"
QkVHSU46VkNBTEVOREFSDQpWRVJTSU9OOjIuMA0KUFJPRElEOi0vL05vdnVzIEV4YW1wbGVzLy9T
QU1QTEUvL0VODQpNRVRIT0Q6Q0FOQ0VMDQpCRUdJTjpWRVZFTlQNClVJRDp3YXZlLWctbWVldGlu
Zy0wMDFAc2FtcGxlLmV4YW1wbGUNCkRUU1RBTVA6MjAyNjAxMTZUMTAwMDAwWg0KRFRTVEFSVDoy
MDI2MDEyMFQxNjAwMDBaDQpEVEVORDoyMDI2MDEyMFQxNzAwMDBaDQpTVU1NQVJZOk5vdnVzIFNB
TVBMRSBQbGFubmluZyBTeW5jDQpPUkdBTklaRVI7Q049QWxleCBTQU1QTEU6bWFpbHRvOmFsZXhA
YnJpZ2h0c2lkZS5leGFtcGxlDQpBVFRFTkRFRTtDTj1TYW0gUml2ZXJhOm1haWx0bzpzYW1AbWVy
aWRpYW5zdXBwbHkuZXhhbXBsZQ0KU1RBVFVTOkNBTkNFTExFRA0KU0VRVUVOQ0U6MQ0KRU5EOlZF
VkVOVA0KRU5EOlZDQUxFTkRBUg0K
--=_wg_cancel_0001--
Specifications
- Method
- CANCEL
- Uid
- wave-g-meeting-001@sample.example
- Wave
- G
Testing contract
Expected to pass- Scenario
- Exercise EML — Calendar Invite Cancel (CANCEL) in its calendar workflow. Cancel twin for the SAMPLE calendar invite — same UID, SEQUENCE bumped, METHOD=CANCEL.
- Expected result
- subject='Cancelled: Novus SAMPLE Planning Sync'; content type=multipart/mixed; MIME leaf parts=2. Declared feature checks: method=CANCEL; uid=wave-g-meeting-001@sample.example. The declared comparison counterpart is eml-wg-invite; preserve the stated difference instead of expecting the container bytes to match.
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 Cancel (CANCEL)” 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,328 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-cancel.eml", "rb"))
print(msg["subject"], msg["from"])Related files
- emlMeeting Invitation with iCalendar (EML)A meeting-invitation email carrying an iCalendar (.ics) VEVENT with METHOD=REQUEST — for testing calendar-invite detection, ICS extraction, and RSVP handling.
- emlBounce / Non-Delivery Report (EML)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.
- emlEmail with Attachment (EML)A multipart/mixed email with a base64-encoded CSV file attachment — for testing attachment detection, decoding, and extraction from an EML message.
- emlEML — 1,024-Octet Header Line With No Fold PointA single header whose value is one 1,001-character token with no whitespace, making the line 1,024 octets — past the 998-octet limit RFC 5322 sets and impossible to fold. Fixed-size line buffers truncate here, and the truncation is silent.
- emlEML — Attachment With No Filename At AllAn 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 binary.
- emlEML — Base64: Accented UTF-8 BodyA 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 is suspect.
Generated by generation/email_wave_g.py. Free for any use, no attribution required, license.