RFC 5804 on A Protocol for Remotely Managing Sieve Scripts

rfc-editor@rfc-editor.org Tue, 13 July 2010 04:25 UTC

Return-Path: <wwwrun@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 014D73A68E3; Mon, 12 Jul 2010 21:25:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.015
X-Spam-Level:
X-Spam-Status: No, score=-2.015 tagged_above=-999 required=5 tests=[AWL=-0.015, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, NO_RELAYS=-0.001]
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 DqXUlrj6e8lw; Mon, 12 Jul 2010 21:25:09 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by core3.amsl.com (Postfix) with ESMTP id 28BF13A6A42; Mon, 12 Jul 2010 21:25:09 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id E45CEE06D7; Mon, 12 Jul 2010 21:25:17 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 5804 on A Protocol for Remotely Managing Sieve Scripts
From: rfc-editor@rfc-editor.org
Message-Id: <20100713042517.E45CEE06D7@rfc-editor.org>
Date: Mon, 12 Jul 2010 21:25:17 -0700
Cc: sieve@ietf.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, 13 Jul 2010 04:25:10 -0000

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

        
        RFC 5804

        Title:      A Protocol for Remotely Managing 
                    Sieve Scripts 
        Author:     A. Melnikov, Ed.,
                    T. Martin
        Status:     Standards Track
        Stream:     IETF
        Date:       July 2010
        Mailbox:    Alexey.Melnikov@isode.com, 
                    timmartin@alumni.cmu.edu
        Pages:      49
        Characters: 103194
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-sieve-managesieve-09.txt

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

Sieve scripts allow users to filter incoming email.  Message stores
are commonly sealed servers so users cannot log into them, yet users
must be able to update their scripts on them.  This document describes
a protocol "ManageSieve" for securely managing Sieve scripts on a
remote server.  This protocol allows a user to have multiple scripts,
and also alerts a user to syntactically flawed scripts.  [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
Association Management Solutions, LLC