Enable UTF8=ACCEPT if the server supports ENABLE (and UTF=ACCEPT). #1617
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
This is written so that net-imap has the option of enabling IMAP4REV2 instead, if available.
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.
This is written so that net-imap has the option of enabling IMAP4REV2 instead, if the IMAP server has that. (IMAP4Rev2 includes the same syntax and functionality.)
With this PR, mikel-mail is able to read a message with UTF8 addresses from a compliant IMAP server, generate a reply and send it. Both net-imap and net-smtp contain the necessary code. At one line of code, this is the smallest such PR I've ever made ;)
(You may wonder about the call to .capable?. It's enough, see RFF5161 page 2. ENABLE is written to allow clients to send a fixed string; the server ignores what it can't enable.)