29 lines
996 B
Plaintext
29 lines
996 B
Plaintext
MBOX-Line: From tjs at psaux.com Fri Jun 11 00:55:21 2010
|
|
To: imap-protocol@u.washington.edu
|
|
From: Tim Showalter <tjs@psaux.com>
|
|
Date: Fri Jun 8 12:34:43 2018
|
|
Subject: [Imap-protocol] IMAP MOVE extension
|
|
In-Reply-To: <4C11E96E.7080502@gulbrandsen.priv.no>
|
|
References: <201006110854.37969.witold.krecicki@firma.o2.pl>
|
|
<4C11E96E.7080502@gulbrandsen.priv.no>
|
|
Message-ID: <4C11EBE9.5070004@psaux.com>
|
|
|
|
On 6/11/10 12:44 AM, Arnt Gulbrandsen wrote:
|
|
> I implemented that a while ago, but I chose to implement only UID MOVE
|
|
> (an atomic uid-based move being what was needed), and you chose to
|
|
> specify only MOVE. Why not UID?
|
|
|
|
Looks like it's there --
|
|
|
|
> Additionally, MOVE command can be directly preceeded by UID command,
|
|
> the sequence set argument is then treated as unique identifiers
|
|
> sequence instead of message sequence numbers as defined in [IMAP4]
|
|
> paragraph 6.4.8.
|
|
|
|
I'm interested in seeing this move forward. It would help both my
|
|
company's server and our clients.
|
|
|
|
Tim
|
|
|
|
|