Fix threading view in Thunderbird (others?) #1304
Merged
Conversation
This file contains 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
Replies sent via SnappyMail break thread view in Thunderbird due to not standard-compliant Reply-To and References headers. * Due to the long IDs, the headers `Reply-To`, `References` (and `Messge-ID`) are split between the header name and its value. According to section RFC5322, section 2.2.3, this may be legal but it obviously causes problems. * On subsequent replies, the parent's ID gets prepended to the `References` header. Section 3.6.4 of the same RFC specifies that the ID should be appended to that header.
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.
Replies sent via SnappyMail break thread view in Thunderbird due to not standard-compliant Reply-To and References headers.
Due to the long IDs, the headers
Reply-To,References(andMessge-ID) are split between the header name and its value. According to section RFC5322, section 2.2.3, this may be legal but it obviously causes problems.On subsequent replies, the parent's ID gets prepended to the
Referencesheader. Section 3.6.4 of the same RFC specifies that the ID should be appended to that header.