RFC 5228 on Sieve: An Email Filtering Language

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

To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 5228 on Sieve: An Email Filtering Language
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, ietf-mta-filters@imc.org
Message-Id: <20080116195117.0F1A810921B@bosco.isi.edu>
Date: Wed, 16 Jan 2008 11:51:17 -0800
Sender: owner-ietf-mta-filters@mail.imc.org
Precedence: bulk


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

        
        RFC 5228

        Title:      Sieve: An Email Filtering Language 
        Author:     P. Guenther, Ed.,
                    T. Showalter, Ed.
        Status:     Standards Track
        Date:       January 2008
        Mailbox:    guenther@sendmail.com, 
                    tjs@psaux.com
        Pages:      42
        Characters: 87531
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-sieve-3028bis-13.txt

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

This document describes a language for filtering email messages at
time of final delivery.  It is designed to be implementable on either
a mail client or mail server.  It is meant to be extensible, simple,
and independent of access protocol, mail architecture, and operating
system.  It is suitable for running on a mail server where users may
not be allowed to execute arbitrary programs, such as on black box
Internet Message Access Protocol (IMAP) servers, as the base language
has no variables, loops, or ability to shell out to external
programs.  [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

...

RFC 5228 on Sieve: An Email Filtering Language rfc-editor