MBOX-Line: From dshaw at jabberwocky.com Mon Nov 23 14:45:45 2015 To: imap-protocol@u.washington.edu From: David Shaw Date: Fri Jun 8 12:34:55 2018 Subject: [Imap-protocol] UID MOVE and untagged OKs In-Reply-To: <1447882210.1528738.443668657.2E2AAB9D@webmail.messagingengine.com> References: <25069F83-83C9-4130-B0D0-6C4FCC37A292@jabberwocky.com> <564BBF09.7050804@teamaol.com> <564BC814.8080409@comaxis.com> <1447817383.3655600.442841513.22BFE21F@webmail.messagingengine.com> <1447882210.1528738.443668657.2E2AAB9D@webmail.messagingengine.com> Message-ID: On Nov 18, 2015, at 4:30 PM, Bron Gondwana wrote: > > On Wed, Nov 18, 2015, at 14:29, Bron Gondwana wrote: >> On Wed, Nov 18, 2015, at 11:36, Jeff McKay wrote: >>> I just tried it and I would agree with David that O365 is indeed behaving as he described - no untagged OK in response to UID MOVE. >> >> I can also confirm this - sorry about the few hour delay, dentist appointment in the middle of all this. >> >> I've bought myself an O365 account and tested it just to see it for myself, this is with openssl s_client >> >> . FETCH 1:* UID >> * 1 FETCH (UID 8) >> . OK FETCH completed. >> . MOVE 1 Extra >> [COPYUID 78 8 1] >> * 1 EXPUNGE >> * 0 EXISTS >> . OK MOVE completed. > > Have heard from someone at Microsoft that they are aware of the problem - so I guess the message got through to whoever needed to know. > > I don't know what their test/deploy cycle looks like - it will be interesting to see how long until the fix makes it out to production. That's great. I am very pleased to hear it. It does seem like the issue has been around for a long time. I found a bug report for this problem from October of 2014: https://github.com/jstedfast/MailKit/issues/115 David