Parse email addresses with non-ASCII UTF8 domain parts #4831
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
Signed-off-by: Robert Stepanek <rsto@fastmailteam.com>
Signed-off-by: Robert Stepanek <rsto@fastmailteam.com>
|
Huh, that success locally but fails in CI. Changing this to Draft until I fixed that. |
ksmurchison
reviewed
Mar 5, 2024
|
Thanks for the |
ksmurchison
approved these changes
Mar 6, 2024
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.
Email addresses having non-ASCII UTF8 domain parts up until now were parsed incorrectly, leading to truncated email addresses being stored in the mailbox cache and returned in JMAP and IMAP.
This fixes the email address parser to parse such domains and bumps the mailbox minor cache version number.