📚 Document COPYUID in tagged vs untagged responses #398
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.
COPYUID
was originally (in theUIDPLUS
extension) only allowed to be sent in the tagged response to the command which copied the messages.Because the move commands atomically combine copy with expunge, the
MOVE
extension changed that for move commands, to recommend sending it as an untagged response prior to the tagged response for the move. This way,EXPUNGE
responses could also be sent prior to the completion of theMOVE
.IMAP4rev2
updates that recommendation to a requirement.However, some of the biggest email providers (most notably, GMail) follow the original
UIDPLUS
extension's requirement and still send theCOPYUID
response with the tagged response, even for move commands.