FA-76429 / Email MIME structure / Member archive

Classify leaf parts as body, inline or attachment: inline images only · case 04

Inline PDFs or audio are placed in the body where the viewer cannot render them.

Member previewVariant 4 · 3 implementations · 8 checks per implementation

Case contract

parts are the leaves of a multipart/mixed message in order: {type, disp, cid, filename}. Rules in order: an explicit "attachment" disposition (case-insensitive) is an attachment even when referenced; a part whose cid is exactly one of html_cids is inline; the first text/* part without a (non-empty) filename is the body; an explicit inline image/* is inline; everything else is an attachment.

Why this case matters

Disposition decides what the reader sees in the message body and what is offered for download.

One recorded failure

Sample boundary fixture

This sample comes from the broken implementation of a controlled reproducer.

Boundary fixture	Actual	Expected	Outcome
inline non-images	`["body", "inline", "inline", "inline"]`	`["body", "attachment", "attachment", "inline"]`	Failed

MEMBER ARCHIVE

The complete case is available to members.

This record includes three runnable implementations, regression fixtures, execution results, and source hashes.

Member access is invitation-based. Sign in with your invited account to inspect the sources.