30 lines
1.2 KiB
Plaintext
30 lines
1.2 KiB
Plaintext
MBOX-Line: From stujenerin at aol.com Wed Feb 6 09:38:27 2013
|
|
To: imap-protocol@u.washington.edu
|
|
From: Stuart Brandt <stujenerin@aol.com>
|
|
Date: Fri Jun 8 12:34:50 2018
|
|
Subject: [Imap-protocol] Clarification on RFC 6851
|
|
Message-ID: <51129513.5080905@aol.com>
|
|
|
|
I'm hoping someone can clarify the following section of the new MOVE
|
|
extension:
|
|
|
|
Because a MOVE applies to a set of messages, it might fail partway
|
|
through the set. Regardless of whether the command is successful in
|
|
moving the entire set, each individual message SHOULD either be moved
|
|
or unaffected. The server MUST leave each message in a state where
|
|
it is in at least one of the source or target mailboxes (no message
|
|
can be lost or orphaned). The server SHOULD NOT leave any message in
|
|
both mailboxes (it would be bad for a partial failure to result in a
|
|
bunch of duplicate messages). This is true even if the server
|
|
returns a tagged NO response to the command.
|
|
|
|
|
|
In the case where a MOVE fails partway through the set and leaves some
|
|
messages moved and others unaffected, does this imply that servers
|
|
SHOULD return a NO in the tagged response, or is OK the more appropriate
|
|
tagged response?
|
|
|
|
Thanks...
|
|
- Stuart
|
|
|