fix: utf8 decoding - #11510
Merged
Merged
Conversation
github-actions
Bot
added
the
tb-team
Contributor
|
✅ Validation Passed: All report and feature-flag labels are correctly set. |
This was referenced Sep 10, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Contribution Summary
Linked Issue/Ticket: resolves #11508
Description
Fix UTF-8 MIME header decoding broken by the Mime4j 0.8.14 update. Raw headers are now explicitly decoded as UTF-8 instead of relying on Mime4j’s ISO-8859-1 toString() behavior.
Adds regression tests for attachment filenames across all affected parsing paths.
AI Disclosure
Select one of the following (mandatory)