RFC 5490 on The Sieve Mail-Filtering Language -- Extensions for Checking Mailbox Status and Accessing Mailbox Metadata

rfc-editor@rfc-editor.org Tue, 31 March 2009 23:09 UTC

Return-Path: <rfc-editor@rfc-editor.org>
X-Original-To: ietf-announce@core3.amsl.com
Delivered-To: ietf-announce@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3229928C1C4 for <ietf-announce@core3.amsl.com>; Tue, 31 Mar 2009 16:09:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -16.924
X-Spam-Level:
X-Spam-Status: No, score=-16.924 tagged_above=-999 required=5 tests=[AWL=0.075, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, USER_IN_DEF_WHITELIST=-15]
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 zPgJLOOsKD+0 for <ietf-announce@core3.amsl.com>; Tue, 31 Mar 2009 16:09:01 -0700 (PDT)
Received: from bosco.isi.edu (bosco.isi.edu [128.9.168.207]) by core3.amsl.com (Postfix) with ESMTP id 4C12D28C1C2 for <ietf-announce@ietf.org>; Tue, 31 Mar 2009 16:09:01 -0700 (PDT)
Received: by bosco.isi.edu (Postfix, from userid 70) id EF10F26B6E6; Tue, 31 Mar 2009 16:09:24 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 5490 on The Sieve Mail-Filtering Language -- Extensions for Checking Mailbox Status and Accessing Mailbox Metadata
From: rfc-editor@rfc-editor.org
Message-Id: <20090331230924.EF10F26B6E6@bosco.isi.edu>
Date: Tue, 31 Mar 2009 16:09:24 -0700
Cc: ietf-mta-filters@imc.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 31 Mar 2009 23:09:02 -0000

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

        
        RFC 5490

        Title:      The Sieve Mail-Filtering Language -- 
                    Extensions for Checking Mailbox Status and 
                    Accessing Mailbox Metadata 
        Author:     A. Melnikov
        Status:     Standards Track
        Date:       March 2009
        Mailbox:    Alexey.Melnikov@isode.com
        Pages:      8
        Characters: 16065
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-melnikov-sieve-imapext-metadata-08.txt

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

This memo defines an extension to the Sieve mail filtering language
(RFC 5228) for accessing mailbox and server annotations, checking for
mailbox existence, and controlling mailbox creation on "fileinto"
action.  [STANDARDS TRACK]

This document is a product of the Sieve Mail Filtering Language 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
USC/Information Sciences Institute