Skip to content

Keep the folders in attachment names that Outlook writes unescaped - #54

Merged
odrobnik merged 1 commit into
mainfrom
claude/swiftmail-1.16-outlook-paths
Oct 9, 2026
Merged

odrobnik merged 1 commit into
mainfrom
claude/swiftmail-1.16-outlook-paths

Conversation

@odrobnik

@odrobnik odrobnik commented Oct 9, 2026

Copy link
Copy Markdown
Contributor

Outlook names a file attached from a folder after its Windows path and doesn't escape the backslashes:

Content-Disposition: attachment;
	filename="zpo-berufung\reference\akt.md"

Read strictly as RFC 2045 quoted pairs, \r becomes r. The 74-attachment mail behind #52 therefore listed zpo-berufungreferenceakt.md, and two LIESMICH.md files in different folders looked the same.

Change

  • SwiftMail pin moves to 88c45cb, which adds Keep backslashes in filenames that Outlook writes unescaped SwiftMail#254 on top of #253. It keeps those backslashes when parsing .eml files. Over IMAP, Dovecot has already dropped them from BODYSTRUCTURE, so fetchStructure restores them from each named part's MIME header. The SwiftMail 1.16.0 tag moves to this commit so the release includes it.

Verified

  • swift test: 63 run, 4 skipped, 0 failures.
  • Against the real server with this build: post fetch 21835 --server drobnik lists zpo-berufung\training\README.md, zpo-berufung\training\entscheidungen\LIESMICH.md, … instead of zpo-berufungtrainingREADME.md. post list is unchanged.

🤖 Generated with Claude Code

Outlook names a file attached from a folder after its Windows path and
doesn't escape the backslashes, so the 74-attachment mail behind #52
listed zpo-berufung\reference\akt.md as zpo-berufungreferenceakt.md and
two LIESMICH.md files in different folders looked the same. SwiftMail
#254 keeps those backslashes for both .eml files and IMAP. It is now part
of the SwiftMail 1.16.0 release, so the pin moves to its commit.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Oct 9, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-10-09T11:19:26.481761Z 4de67a4 PR opened
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@odrobnik
odrobnik merged commit 412377c into main Oct 9, 2026
2 checks passed
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