Version: unspecified (using Devel) OS: Linux As with Bug 204653 - Microsoft Exchange supports UIDPLUS, but doesn't report it in CAPABILITY: * OK The Microsoft Exchange IMAP4 service is ready. . CAPABILITY * CAPABILITY IMAP4 IMAP4rev1 AUTH=NTLM AUTH=GSSAPI AUTH=PLAIN IDLE NAMESPACE LITERAL+ . OK CAPABILITY completed. . LOGIN [user] [password] . OK LOGIN completed. . CAPABILITY * CAPABILITY IMAP4 IMAP4rev1 AUTH=NTLM AUTH=GSSAPI AUTH=PLAIN IDLE NAMESPACE LITERAL+ . OK CAPABILITY completed. . NOOP . OK NOOP completed. . SELECT INBOX * 3 EXISTS * 0 RECENT * FLAGS (\Seen \Answered \Flagged \Deleted \Draft $MDNSent) * OK [PERMANENTFLAGS (\Seen \Answered \Flagged \Deleted \Draft $MDNSent)] Permanent flags * OK [UIDVALIDITY 3508] UIDVALIDITY value * OK [UIDNEXT 910] The next unique identifier value . OK [READ-WRITE] SELECT completed. . FETCH 1 UID * 1 FETCH (UID 889) . OK FETCH completed. . UID FETCH 889 FLAGS * 1 FETCH (FLAGS (\Seen) UID 889) . OK FETCH completed. Reproducible: Always
Actually, having actually looked up RFC 4315, the commands suggested on Bug 204653 don't actually check whether the server secretly supports the UIDPLUS extension. I tested the actual UID EXPUNGE command, and it returns BAD [uid argument].
I'm reopening and asking if someone who can test can test appending to a message and copying a message and post the servers output here (the same as above but including the APPEND and COPY command). The reason is that we do not use more then the extended response codes from these commands from the RFC.
*** This bug has been marked as a duplicate of bug 236109 ***