MBOX-Line: From witold.krecicki at firma.o2.pl  Fri Jun 11 02:15:18 2010
To: imap-protocol@u.washington.edu
From: Witold =?utf-8?q?Kr=C4=99cicki?= <witold.krecicki@firma.o2.pl>
Date: Fri Jun  8 12:34:43 2018
Subject: [Imap-protocol] IMAP MOVE extension
In-Reply-To: <23852.1276246771.199346@puncture>
References: <201006110854.37969.witold.krecicki@firma.o2.pl>
	<23852.1276246771.199346@puncture>
Message-ID: <201006111115.19660.witold.krecicki@firma.o2.pl>

On Friday 11 of June 2010 10:59:31 Dave Cridland wrote:
> Depending on your server design, this is either very easy, or else
> very hard - of course, since it's optional, it'd seem likely that
> where it's hard it'd not be supported.
That's sure, that's why it's an option.  In most popular IMAP servers that use 
Maildirs this is a simple 'move' operation, with I/O cost of next to nothing 
(assuming that the whole user account is on one FS of course).

> One thing that concerns me is that there is no way to undo this
> operation - traditionally, only EXPUNGE and DELETE have been
> irrevocable actions in IMAP, this adds one more.
I don't see problem with that. And it is still revocable as long as we don't 
care for changed UID (you can always select second mailbox and move messages 
back). No data is harmed here.

> The way to combat this is to make it merely mark \Deleted the
> original message - except then this eradicates any benefit to the
> command at all for clients. (Since one could either do MOVE/UID
> EXPUNGE, or else COPY+STORE/UID EXPUNGE).
That destroys the whole idea of atomic MOVE command, from both server and 
client side.

> And there has to be very significant advantage for clients, across a
> wide deployment, for most clients to bother implementing it - right
> now, I don't see it.
Have you ever tried to 'move to trash' eg. 2000 messages from inbox?
With current copy/store/expunge routine it takes (at least on servers that 
I've tested) really really long times. 

Another real life example is a situation when user wants to move contents of 
his INBOX to 'old-mail' mailbox with quota enabled and INBOX larger than half 
of his quota.

Other thing is that most of the client support 'move' operation by means of 
cp/st/ex, and adding support for simplified 'MOVE' mode should not be such a 
huge programming effort.

-- 
Witold Kr?cicki

Grupa o2 Sp??ka z o.o., ul. Jutrzenki 177, 02-231 Warszawa,
KRS 0000140518, S?d Rejonowy dla m.st. Warszawy, 
Kapita? zak?adowy 377.298,00 z?., NIP 521-31-11-513

