Internet Message Access Protocol (IMAP) - MOVE Extension
draft-ietf-imapmove-command-03

The information below is for an old version of the document
Document Type Active Internet-Draft (imapmove WG)
Last updated 2012-11-21
Replaces draft-gulbrandsen-imap-move
Stream IETF
Intended RFC status Proposed Standard
Formats plain text pdf html
Stream WG state Submitted to IESG for Publication
Consensus Unknown
Document shepherd Alexey Melnikov
Shepherd write-up Show (last changed 2012-11-07)
IESG IESG state IESG Evaluation
Telechat date
Needs 5 more YES or NO OBJECTION positions to pass.
Responsible AD Barry Leiba
Send notices to imapmove-chairs@tools.ietf.org, draft-ietf-imapmove-command@tools.ietf.org
Network Working Group                                     A. Gulbrandsen
Internet-Draft
Intended status: Standards Track                                N. Freed
Expires: May 25, 2013                                             Oracle
                                                       November 21, 2012

        Internet Message Access Protocol (IMAP) - MOVE Extension
                     draft-ietf-imapmove-command-03

Abstract

   This document defines an IMAP extension consisting of two new
   commands, MOVE and UID MOVE, that are used to move messages from one
   mailbox to another.

Status of this Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on May 25, 2013.

Copyright Notice

   Copyright (c) 2012 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Gulbrandsen & Freed       Expires May 25, 2013                  [Page 1]
Internet-Draft            IMAP - MOVE Extension            November 2012

1.  Introduction

   This document defines an IMAP [RFC3501] extension to facilitate
   moving messages from one mailbox to another.  This is accomplished by
   defining a new MOVE command and extending the UID command to allow
   UID MOVE.

   A move function is not provided in the base IMAP specification, so
   clients have instead had to use a combination of the UID STORE, UID
   COPY and EXPUNGE commands to perform this very common operation.
   This has meant needing to cope with partial failures and side effects
   that can occur when multiple commands are involved.

   The MOVE extension is present in any IMAP4 implementation which
   returns "MOVE" as one of the supported capabilities to the CAPABILITY
   command.

2.  Conventions Used in This Document

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in [RFC2119].

   Formal syntax is specified using ABNF [RFC5234].

   Example lines prefaced by "C:" are sent by the client and ones
   prefaced by "S:" by the server.

3.  MOVE and UID MOVE

3.1.  MOVE Command

   Arguments: sequence set
              mailbox name

   Responses: no specific responses for this command

   Result: OK - move completed

           NO - move error: can't move those messages or to that name

           BAD - command unknown or arguments invalid

Gulbrandsen & Freed       Expires May 25, 2013                  [Page 2]
Internet-Draft            IMAP - MOVE Extension            November 2012

3.2.  UID MOVE Command

   This extends the first form of the UID command (see [RFC3501],
   Section 6.4.8) to add the MOVE command, defined above, as a valid
   argument.

3.3.  Semantics of MOVE and UID MOVE

   The MOVE command takes two arguments: a message set (sequence numbers
   for MOVE, UIDs for UID MOVE) and a named mailbox.  Each message
   included in the set is moved, rather than copied, from the selected
   (source) mailbox to the named (target) mailbox.

   This means that a new message is created in the target mailbox, with
   a new UID, the original message is removed from the source mailbox,
   and it appears to the client as a single action.  This has the same
   effect for each message as this sequence:

   1.  [UID] COPY

   2.  [UID] STORE +FLAGS.SILENT \DELETED
Show full document text