wasm-demo/demo/ermis-f/imap-protocol/cur/1600095101.22807.mbox:2,S

35 lines
1.5 KiB
Plaintext

MBOX-Line: From witold.krecicki at firma.o2.pl Fri Jun 11 09:26:49 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: <alpine.OSX.2.00.1006110841480.662@hsinghsing.panda.com>
References: <201006110854.37969.witold.krecicki@firma.o2.pl>
<23852.1276246771.199346@puncture>
<alpine.OSX.2.00.1006110841480.662@hsinghsing.panda.com>
Message-ID: <201006111826.49492.witold.krecicki@firma.o2.pl>
On Friday 11 of June 2010 17:57:05 Mark Crispin wrote:
> On Fri, 11 Jun 2010, 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.
>
> Correct.
>
> Commands in IMAP are atomic; thus this MOVE operation must be atomic.
> It is simply impossible to do an atomic MOVE with many stores.
>
> Note that not even a one-file/one-message store (ala maildir) can do MOVE
> atomically. Each file has to be renamed separately. That's not atomic!
Also, I've originally put a note about atomicity of MOVE operation in this
draft, but commented it out as too controversial. As it seems the lack of this
note is controversial ;)
--
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