RFC 5436 on Sieve Notification Mechanism: mailto

rfc-editor@rfc-editor.org Sun, 01 February 2009 03:53 UTC

Return-Path: <ietf-announce-bounces@ietf.org>
X-Original-To: ietf-announce-archive@megatron.ietf.org
Delivered-To: ietfarch-ietf-announce-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C2A263A6AD4; Sat, 31 Jan 2009 19:53:02 -0800 (PST)
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 1B6443A6AD4 for <ietf-announce@core3.amsl.com>; Sat, 31 Jan 2009 19:53:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -16.494
X-Spam-Level:
X-Spam-Status: No, score=-16.494 tagged_above=-999 required=5 tests=[AWL=0.505, 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 tv1H0lLov8FL for <ietf-announce@core3.amsl.com>; Sat, 31 Jan 2009 19:53:01 -0800 (PST)
Received: from bosco.isi.edu (bosco.isi.edu [128.9.168.207]) by core3.amsl.com (Postfix) with ESMTP id 66E573A6AB6 for <ietf-announce@ietf.org>; Sat, 31 Jan 2009 19:53:01 -0800 (PST)
Received: by bosco.isi.edu (Postfix, from userid 70) id 1F96E2044BD; Sat, 31 Jan 2009 19:52:43 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 5436 on Sieve Notification Mechanism: mailto
From: rfc-editor@rfc-editor.org
Message-Id: <20090201035243.1F96E2044BD@bosco.isi.edu>
Date: Sat, 31 Jan 2009 19:52:43 -0800
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/pipermail/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>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ietf-announce-bounces@ietf.org
Errors-To: ietf-announce-bounces@ietf.org

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

        
        RFC 5436

        Title:      Sieve Notification Mechanism: mailto 
        Author:     B. Leiba, M. Haardt
        Status:     Standards Track
        Date:       January 2009
        Mailbox:    leiba@watson.ibm.com, 
                    michael.haardt@freenet.ag
        Pages:      12
        Characters: 26519
        Updates:    RFC3834

        I-D Tag:    draft-ietf-sieve-notify-mailto-10.txt

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

This document describes a profile of the Sieve extension for
notifications, to allow notifications to be sent by electronic mail.  
[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


_______________________________________________
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/ietf-announce