[MORG] Protocol Action: 'IMAP LIST extension for special-use mailboxes' to Proposed Standard (draft-ietf-morg-list-specialuse-06.txt)

The IESG <iesg-secretary@ietf.org> Mon, 20 December 2010 17:30 UTC

Return-Path: <iesg-secretary@ietf.org>
X-Original-To: morg@core3.amsl.com
Delivered-To: morg@core3.amsl.com
Received: from localhost (localhost []) by core3.amsl.com (Postfix) with ESMTP id 3F6FA3A6907; Mon, 20 Dec 2010 09:30:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.53
X-Spam-Status: No, score=-102.53 tagged_above=-999 required=5 tests=[AWL=0.069, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([]) by localhost (core3.amsl.com []) (amavisd-new, port 10024) with ESMTP id rQDo1PNy8aYe; Mon, 20 Dec 2010 09:30:48 -0800 (PST)
Received: from [] (localhost []) by core3.amsl.com (Postfix) with ESMTP id E53333A6A90; Mon, 20 Dec 2010 09:30:47 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 3.10
Message-ID: <20101220173047.3034.89654.idtracker@localhost>
Date: Mon, 20 Dec 2010 09:30:47 -0800
Cc: morg chair <morg-chairs@tools.ietf.org>, morg mailing list <morg@ietf.org>, Internet Architecture Board <iab@iab.org>, RFC Editor <rfc-editor@rfc-editor.org>
Subject: [MORG] Protocol Action: 'IMAP LIST extension for special-use mailboxes' to Proposed Standard (draft-ietf-morg-list-specialuse-06.txt)
X-BeenThere: morg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Messaging Organization <morg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/morg>, <mailto:morg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/morg>
List-Post: <mailto:morg@ietf.org>
List-Help: <mailto:morg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/morg>, <mailto:morg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Dec 2010 17:30:49 -0000

The IESG has approved the following document:
- 'IMAP LIST extension for special-use mailboxes'
  (draft-ietf-morg-list-specialuse-06.txt) as a Proposed Standard

This document is the product of the Message Organization Working Group.

The IESG contact persons are Alexey Melnikov and Peter Saint-Andre.

A URL of this Internet Draft is:

Technical Summary

   Some IMAP message stores include special-use mailboxes, such as those
   used to hold draft messages or sent messages.  Many mail clients
   allow users to specify where draft or sent messages should be put,
   but configuring them requires that the user know which mailboxes the
   server has set aside for these purposes.  This extension adds new
   mailbox attributes that a server MAY include in IMAP LIST command
   responses to identify special-use mailboxes to the client, easing

Working Group Summary 

   There were some concerns about the number of IMAP CAPABILITY strings and
   about moving of existing special-use attributes, but there have been no
   complaints about the end result.

Document Quality 

   This extension is based on Google's XLIST extension for GMail. Google has
   expressed interest in implementing this extension as well, among several
   other server vendors. Many clients have already implemented XLIST, and they
   will either automatically or with very small modifications gain support for
   this extension


   Timo Sirainen is the Document Shepherd for this document.
   Alexey Melnikov is the Responsible Area Director.

RFC Editor Note

In Section 7, please replace the 1st paragraph to read:

   LIST response: There are no security issues with conveying special-
   use information to a client.

   LIST response:
   Conveying special-use information to a client exposes a small bit of
   extra information that could be of value to an attacker.  Knowing, for
   example, that a particular mailbox contains pointers to every message
   the user has (\All) might be of particular value.  If the IMAP channel
   is not protected from passive eavesdropping, this could be an issue.

In Section 8.6:

   Name: /shared/specialuse

   Name: /private/specialuse