Repository navigation
RFC page: RFC 2180 COPY rule and RFC 5530 response codes - #240
Merged
Merged
Conversation
Collaborator
|
#240 (6331ede): two corrections in the RFC 5530 row before merge.
The RFC 2180 row reads right. |
Contributor
Author
|
ALREADYEXISTS removed: it is only sent by ManageSieve (managesieve/session.go), not by IMAP. PARSE stays out of this row: it is an RFC 3501 response code (§7.1), not one RFC 5530 defines, and the 3501 row already covers it. |
Collaborator
This file contains hidden or 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
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.
Two IMAP rows for the 2.4.5 changes:
NO [EXPUNGEISSUED](§4.4.1).