EML — S/MIME-Shaped Unsigned Placeholder
S/MIME-shaped SAMPLE with a placeholder PKCS7 part (not a real signature) for MIME structure tests.
MIME-Version: 1.0
From: Alex SAMPLE <alex@brightside.example>
To: Sam Rivera <sam@meridiansupply.example>
Subject: S/MIME-shaped SAMPLE (unsigned placeholder)
Date: Fri, 17 Jan 2026 09:00:00 -0800
Message-ID: <wave-g-smime-001@brightside.example>
Content-Type: multipart/signed; boundary="=_wg_smime_0001";
protocol="application/pkcs7-signature"; micalg="sha-256"
--=_wg_smime_0001
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
VGhpcyBpcyBhbiB1bnNpZ25lZCBTL01JTUUtc2hhcGVkIFNBTVBMRSBib2R5Lgo=
--=_wg_smime_0001
Content-Type: application/pkcs7-signature
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Tk9WVVMtU0FNUExFLVBLQ1M3LVNJR05BVFVSRS1QTEFDRUhPTERFUi1OT1QtUkVBTA==
--=_wg_smime_0001--
Specifications
- Structure
- multipart/signed
- Signature
- placeholder
- Valid Smime
- false
- Wave
- G
Testing contract
Expected to pass- Scenario
- Exercise EML — S/MIME-Shaped Unsigned Placeholder in its smime workflow. S/MIME-shaped SAMPLE with a placeholder PKCS7 part (not a real signature) for MIME structure tests.
- Expected result
- subject='S/MIME-shaped SAMPLE (unsigned placeholder)'; content type=multipart/signed; MIME leaf parts=2. Declared feature checks: structure=multipart/signed; signature=placeholder; validSmime=False.
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 — S/MIME-Shaped Unsigned Placeholder” 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: multipart/signed. 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("unsigned-placeholder.eml", "rb"))
print(msg["subject"], msg["from"])Related files
- 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.
- emlEML — Base64: From-Line and Lone DotA 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.