Send IMAP ID only after authentication #7517
Closed
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
|
I get the idea, but there's a plugin that sets |
|
Implemented in 5975742. |
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.
In case of IMAP proxy, that is doing authentication and routing, receiving ID command may result in
BAD Invalid commanderror, as IMAP proxy does not yet know which server should receive the communications. Even if proxies would return correct output for ID command, the "name" field returned would not necessarily be the same as for "name" field value after authenticating.This applies to Nginx + Dovecot stack.
iPhone Mail, Mac OS X Mail, Microsoft Outlook, Thunderbird, and other major (as 30+ minor) MUAs are sending ID command after authenticating, or even delay it until after NAMESPACE.