fix multibyte handling in imap literals and address splitting, improve unit tests #1230
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
…trings, fix imap unit tests and add tests for recent bugs: accidentally reading next lines of literals and not splitting addresses correctly
This was referenced Sep 9, 2024
|
Supersedes: #1217 |
|
Worth mentioning that this PR should also fix issue #1119 |
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 imap::read_literal to work on 7-bit bytes rather than multibyte strings, fix imap unit tests and add tests for recent bugs: accidentally reading next lines of literals and not splitting addresses correctly