fix(composer): Forwarding emails with attachments#12453
Merged
Conversation
Signed-off-by: Daniel Kesselberg <mail@danielkesselberg.de>
Contributor
Author
|
/backport to stable5.7 |
ChristophWurst
approved these changes
Feb 18, 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
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.
Fix #12374
STR:
The code path was never executed on Mail 5.6, because the response from the messages api doesn't include any details about attachments.
Since Mail 5.7 (c.f. #11596) the api response does include a list of attachments again, making code path active again.
However, the composer already set the attachments and the backend is not able to process the given list of attachments because information are missing.