Skip to content

fix(email): isolate recipient metadata between message elements - #4820

Draft
Afloat16 wants to merge 1 commit into
Unstructured-IO:mainfrom
Afloat16:Afloat16/email-metadata-ownership-20261121
Draft

Afloat16 wants to merge 1 commit into
Unstructured-IO:mainfrom
Afloat16:Afloat16/email-metadata-ownership-20261121

Conversation

@Afloat16

@Afloat16 Afloat16 commented Nov 21, 2026 •

Copy link
Copy Markdown
Contributor

Summary

EML and MSG body elements reuse mutable sender/recipient lists from shared message metadata. Editing or redacting one element can therefore change another element, and MSG changes can reach the partitioning context itself.

Copy message metadata when applying it to each body element. The public ElementMetadata.update() dictionary-like contract and attachment handling stay unchanged.

Validation

  • All five new ownership regressions fail on the base revision and pass after the fix.
  • Real EML documents cover From/To/Cc/Bcc lists; a MSG partitioner regression also verifies the source context stays unchanged.
  • Relevant EML/MSG suites: 128 passed, 30 attachment cases deselected.
  • Full-repository Ruff 0.15.10 lint and format checks pass.

Draft pending the full repository test gate.

Checklist

  • Conventional user-facing title.
  • Maintainer: apply the bug label.
  • Full repository test gate.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant