[MORG] RFC 6154 on IMAP LIST Extension for Special-Use Mailboxes

rfc-editor@rfc-editor.org Thu, 03 March 2011 18:07 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: morg@core3.amsl.com
Delivered-To: morg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3E1543A6A2B; Thu, 3 Mar 2011 10:07:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.102
X-Spam-Level:
X-Spam-Status: No, score=-102.102 tagged_above=-999 required=5 tests=[AWL=-0.102, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BYnmaXZ68BFh; Thu, 3 Mar 2011 10:06:58 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by core3.amsl.com (Postfix) with ESMTP id C532B3A682C; Thu, 3 Mar 2011 10:06:57 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 0EA12E073B; Thu, 3 Mar 2011 10:08:06 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20110303180806.0EA12E073B@rfc-editor.org>
Date: Thu, 03 Mar 2011 10:08:06 -0800
Cc: morg@ietf.org, rfc-editor@rfc-editor.org
Subject: [MORG] RFC 6154 on IMAP LIST Extension for Special-Use Mailboxes
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: Thu, 03 Mar 2011 18:07:01 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 6154

        Title:      IMAP LIST Extension for Special-Use 
                    Mailboxes 
        Author:     B. Leiba, J. Nicolson
        Status:     Standards Track
        Stream:     IETF
        Date:       March 2011
        Mailbox:    barryleiba@computer.org, 
                    nicolson@google.com
        Pages:      12
        Characters: 25544
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-morg-list-specialuse-06.txt

        URL:        http://www.rfc-editor.org/rfc/rfc6154.txt

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
optional mailbox attributes that a server may include in IMAP LIST
command responses to identify special-use mailboxes to the client,
easing configuration.  [STANDARDS-TRACK]

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

This is now a Proposed Standard Protocol.

STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Internet
Official Protocol Standards (STD 1) for the standardization state and
status of this protocol.  Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC