Skip to main content

Sieve Email Filtering -- Subaddress Extension
draft-murchison-sieve-subaddress-06

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 an RFC.
Author Kenneth Murchison
Last updated 2018-07-18 (Latest revision 2003-03-31)
Stream Internet Engineering Task Force (IETF)
Formats
Stream WG state (None)
Document shepherd (None)
IESG IESG state RFC 3598 (Proposed Standard)
Consensus boilerplate Unknown
Telechat date (None)
Responsible AD Ned Freed
IESG note Published as RFC 3598 10-Sep-2003
Send notices to (None)
draft-murchison-sieve-subaddress-06
A new Request for Comments is now available in online RFC libraries.

        RFC 3598

        Title:      Sieve Email Filtering -- Subaddress Extension
        Author(s):  K. Murchison
        Status:     Standards Track
        Date:       September 2003
        Mailbox:    ken@oceana.com
        Pages:      6
        Characters: 11151
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-murchison-sieve-subaddress-06.txt

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

On email systems that allow for "subaddressing" or "detailed
addressing" (e.g., "ken+sieve@example.org"), it is sometimes desirable
to make comparisons against these sub-parts of addresses.  This
document defines an extension to the Sieve mail filtering language
that allows users to compare against the user and detail parts of an
address. 

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.