FA-76779 / Email MIME structure / Member archive

Choose non-colliding boundaries for nested multiparts: length limit · case 04

Boundaries longer than the 70-character limit are generated.

Member previewVariant 4 · 3 implementations · 6 checks per implementation

Case contract

Multipart nodes have "parts", leaves have "text". Nodes are visited depth-first (pre-order) and a single counter produces candidates base_1, base_2, ... A candidate is rejected when it occurs in any text anywhere below the node, when it is a prefix of an ancestor boundary or an ancestor boundary is a prefix of it, and a candidate longer than 70 characters makes that node's boundary None (its subtree gets none). Result: boundaries in visiting order.

Why this case matters

A boundary that appears inside a part, or that extends an outer boundary, splits the message at the wrong place.

One recorded failure

Sample boundary fixture

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

Boundary fixture	Actual	Expected	Outcome
seventy-one characters	`["yyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyy_1"]`	`[null]`	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.