Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

COPYUID is returned in an untagged response #2114

Closed
gyurco opened this issue Aug 23, 2017 · 1 comment

Comments

Projects
None yet
1 participant
@gyurco
Copy link

commented Aug 23, 2017

RFC2359 says
Successful COPY and UID COPY commands return a COPYUID response code
in the tagged OK response whenever at least one message was copied.

However cyrus 3.0.x returns COPYUID in an untagged response, as below:

[23-Aug-2017 11:45:32 +0200]: [EE2A] C: A0017 UID MOVE 59667 "T&APY-r&APY-lt elemek"
[23-Aug-2017 11:45:32 +0200]: [EE2A] S: * OK [COPYUID 1304109194 59667 4484] Completed
[23-Aug-2017 11:45:32 +0200]: [EE2A] S: * 217 EXPUNGE
[23-Aug-2017 11:45:32 +0200]: [EE2A] S: A0017 OK Completed

This breaks Kolab for example.

@gyurco

This comment has been minimized.

Copy link
Author

commented Aug 23, 2017

Ok, seems not a bug (RFC6851):

Servers implementing UIDPLUS are also advised to send the COPYUID
response code in an untagged OK before sending EXPUNGE or moved
responses. (Sending COPYUID in the tagged OK, as described in the
UIDPLUS specification, means that clients first receive an EXPUNGE
for a message and afterwards COPYUID for the same message. It can be
unnecessarily difficult to process that sequence usefully.)

@gyurco gyurco closed this Aug 23, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.