Skip to content

Handle nested literals in IMAP FETCH values - #122

Open
mpscholten wants to merge 2 commits into
qnikst:masterfrom
mpscholten:codex/fetch-nested-literals
Open

Handle nested literals in IMAP FETCH values#122
mpscholten wants to merge 2 commits into
qnikst:masterfrom
mpscholten:codex/fetch-nested-literals

Conversation

@mpscholten

@mpscholten mpscholten commented Aug 6, 2026

Copy link
Copy Markdown
Contributor

Summary

  • stream byte-counted IMAP literals nested inside parenthesized FETCH values such as BODYSTRUCTURE
  • preserve literal payload bytes and continuation-line separators in the returned value
  • keep parentheses and quotes inside literal payloads from affecting the surrounding parser state

Without this, valid BODYSTRUCTURE responses containing literal MIME parameters fail with cannot parse FETCH value.

Test plan

  • cabal test all --offline
  • 50/50 IMAP parser tests pass
  • regression coverage includes a literal filename, continuation-line delimiter preservation, and literal payload containing parser-significant parentheses and quotes

@chatgpt-codex-connector

Copy link
Copy Markdown

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, add credits to your account and enable them for code reviews in your settings.

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