MBOX-Line: From brong at fastmail.fm  Wed Nov 18 13:30:10 2015
To: imap-protocol@u.washington.edu
From: Bron Gondwana <brong@fastmail.fm>
Date: Fri Jun  8 12:34:55 2018
Subject: [Imap-protocol] UID MOVE and untagged OKs
In-Reply-To: <1447817383.3655600.442841513.22BFE21F@webmail.messagingengine.com>
References: <25069F83-83C9-4130-B0D0-6C4FCC37A292@jabberwocky.com>
	<564BBF09.7050804@teamaol.com>
	<CABa8R6tSWdWpSc2Xxfp+tWVk=GGRHYsdX-YmGXPVoAGCBBdPQw@mail.gmail.com>
	<564BC814.8080409@comaxis.com>
	<1447817383.3655600.442841513.22BFE21F@webmail.messagingengine.com>
Message-ID: <1447882210.1528738.443668657.2E2AAB9D@webmail.messagingengine.com>

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.

Bron.

--
? Bron Gondwana
? brong@fastmail.fm
 
 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman13.u.washington.edu/pipermail/imap-protocol/attachments/20151119/38f583d5/attachment.html>
