RFC 5230 on Sieve Email Filtering: Vacation Extension

rfc-editor@rfc-editor.org Wed, 16 January 2008 20:10 UTC

Return-path: <owner-ietf-mta-filters@mail.imc.org>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1JFEb8-0008Ap-7H for sieve-archive-Aet6aiqu@lists.ietf.org; Wed, 16 Jan 2008 15:10:54 -0500
Received: from balder-227.proper.com ([192.245.12.227]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JFEb7-0001Fy-IS for sieve-archive-Aet6aiqu@lists.ietf.org; Wed, 16 Jan 2008 15:10:54 -0500
Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id m0GJpbdJ014703 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 16 Jan 2008 12:51:37 -0700 (MST) (envelope-from owner-ietf-mta-filters@mail.imc.org)
Received: (from majordom@localhost) by balder-227.proper.com (8.13.5/8.13.5/Submit) id m0GJpbIv014702; Wed, 16 Jan 2008 12:51:37 -0700 (MST) (envelope-from owner-ietf-mta-filters@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-mta-filters@mail.imc.org using -f
Received: from bosco.isi.edu (bosco.isi.edu [128.9.168.207]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id m0GJpbKE014695 for <ietf-mta-filters@imc.org>; Wed, 16 Jan 2008 12:51:37 -0700 (MST) (envelope-from rfc-editor@rfc-editor.org)
Received: by bosco.isi.edu (Postfix, from userid 70) id 0B60B10921F; Wed, 16 Jan 2008 11:51:37 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 5230 on Sieve Email Filtering: Vacation Extension
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, ietf-mta-filters@imc.org
Message-Id: <20080116195137.0B60B10921F@bosco.isi.edu>
Date: Wed, 16 Jan 2008 11:51:37 -0800
Sender: owner-ietf-mta-filters@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-mta-filters/mail-archive/>
List-ID: <ietf-mta-filters.imc.org>
List-Unsubscribe: <mailto:ietf-mta-filters-request@imc.org?body=unsubscribe>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 41c17b4b16d1eedaa8395c26e9a251c4


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

        
        RFC 5230

        Title:      Sieve Email Filtering: Vacation Extension 
        Author:     T. Showalter, N. Freed, Ed.
        Status:     Standards Track
        Date:       January 2008
        Mailbox:    tjs@psaux.com, 
                    ned.freed@mrochek.com
        Pages:      16
        Characters: 29822
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-sieve-vacation-06.txt

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

This document describes an extension to the Sieve email filtering
language for an autoresponder similar to that of the Unix "vacation"
command for replying to messages.  Various safety features are
included to prevent problems such as message loops.  [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 list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 

help: ways_to_get_rfcs. For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

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

Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


The RFC Editor Team
USC/Information Sciences Institute

...