Skip to main content

Sieve Extension: Relational Tests
draft-segmuller-sieve-relation-02

The information below is for an old version of the document that is already published as an RFC.
Document Type
This is an older version of an Internet-Draft that was ultimately published as RFC 3431.
Author Wolfgang Segmuller
Last updated 2015-10-14 (Latest revision 2002-05-15)
RFC stream Internet Engineering Task Force (IETF)
Formats
Stream WG state (None)
Document shepherd (None)
IESG IESG state RFC 3431 (Proposed Standard)
Consensus boilerplate Unknown
Telechat date (None)
Responsible AD Ned Freed
IESG note published 6-Dec-2002
Send notices to (None)
draft-segmuller-sieve-relation-02
A new Request for Comments is now available in online RFC libraries.

        RFC 3431
                                
        Title:      Sieve Extension: Relational Tests
        Author(s):  W. Segmuller
        Status:     Standards Track
        Date:       December 2002
        Mailbox:    whs@watson.ibm.com
        Pages:      8
        Characters: 12849
        Updates/Obsoletes/SeeAlso:    None
                                
        I-D Tag:    draft-segmuller-sieve-relation-02.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3431.txt

This document describes the RELATIONAL extension to the Sieve mail
filtering language defined in RFC 3028.  This extension extends
existing conditional tests in Sieve to allow relational operators.
In addition to testing their content, it also allows for testing of
the number of entities in header and envelope fields.

This is now a Proposed Standard Protocol.

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.echo 
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.