Sieve Working Group                                         K. Murchison
Internet-Draft                                        Oceana Matrix Ltd.
Obsoletes: 3598 (if approved)                           February 7,                         September 12, 2005
Expires: August 11, 2005 March 16, 2006

             Sieve Email Filtering -- Subaddress Extension

Status of this Memo

   This document is an Internet-Draft and is subject to all provisions
   of Section 3 of RFC 3667.

   By submitting this Internet-Draft, each author represents that any
   applicable patent or other IPR claims of which he or she is aware
   have been or will be disclosed, and any of which he or she become becomes
   aware will be disclosed, in accordance with
   RFC 3668. Section 6 of BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF), its areas, and its working groups.  Note that
   other groups may also distribute working documents as
   Internet-Drafts. Internet-

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   The list of current Internet-Drafts can be accessed at

   The list of Internet-Draft Shadow Directories can be accessed at

   This Internet-Draft will expire on August 11, 2005. March 16, 2006.

Copyright Notice

   Copyright (C) The Internet Society (2005).


   On email systems that allow for "subaddressing" or "detailed
   addressing" (e.g., ""), 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.

Meta-information on this document
   This information is intended to facilitate discussion.  It will be
   removed when this document leaves the Internet-Draft stage.

   This document is intended to be an update to the existing
   "subaddress" extension to the Sieve mail filtering language,
   available from the RFC repository as
   <> and

   This document and the Sieve language itself are being discussed on
   the MTA Filters mailing list at <>.
   Subscription requests can be sent to
   <> (send an
   email message with the word "subscribe" in the body).  More
   information on the mailing list along with a WWW archive of back
   messages is available at <>.

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  4
   2.  Capability Identifier  . . . . . . . . . . . . . . . . . . . .  5
   3.  Subaddress Comparisons . . . . . . . . . . . . . . . . . . . .  6
   4.  IANA Considerations  . . . . . . . . . . . . . . . . . . . .   8 .  9
   5.  Security Considerations  . . . . . . . . . . . . . . . . . .   9 . 10
   6.  Normative References . . . . . . . . . . . . . . . . . . . .   9
        Author's Address . . . 10
   Appendix A.  Acknowledgments . . . . . . . . . . . . . . . . . . .   9
   A.   Acknowledgments 11
   Appendix B.  Changes since RFC3598 . . . . . . . . . . . . . . . . 12
   Author's Address . . . . . .  10
   B.   Changes since RFC3598 . . . . . . . . . . . . . . . . . . .  11 13
   Intellectual Property and Copyright Statements . . . . . . .  12 . . . 14

1.  Introduction

   Subaddressing is the practice of appending some "detail" information
   to augmenting (either by prefix or
   suffix) the local-part of an [RFC2822] address with some "detail"
   information to indicate that the message should be delivered to the
   mailbox specified by the "detail" information.  The "detail" information is prefixed with a special  A "separator character"
   character sequence" (typically "+") which "+"), forms the boundary between the
   "user" (original local-part) and the "detail" sub-parts of the address,
   much like the "@" character forms the boundary between the local-part
   and domain.

   Typical uses of subaddressing might be:

   o  A message addressed to "" is delivered into a
      mailbox called "sieve" belonging to the user "ken".

   o  A message addressed to "" is delivered to
      the voice mailbox number "123" at phone number "5551212".

   This document describes an extension to the Sieve language defined by
   [I-D.ietf-sieve-3028bis] for comparing against the "user" and
   "detail" sub-parts of an address.

   Conventions for notations are as in [RFC3028] [I-D.ietf-sieve-3028bis] section
   1.1, including use of [RFC2119].

2.  Capability Identifier

   The capability string associated with the extension defined in this
   document is "subaddress".

3.  Subaddress Comparisons

   Commands that act exclusively on addresses may take the optional
   tagged arguments ":user" and ":detail" to specify what sub-part of
   the local-part of the address will be acted upon.

      NOTE: In most cases, the envelope "to" address is the preferred
      address to examine for subaddress information when the desire is
      to sort messages based on how they were addressed so as to get to
      a specific recipient.  The envelope address is, after all, the
      reason a given message is being processed by a given sieve script
      for a given user.  This is particularly true when mailing lists,
      aliases, and "virtual domains" are involved since the envelope may
      be the only source of detail information for the specific

      NOTE: Because the construction of detailed addresses can be site
      and/or implementation specific, using the subaddress extension on
      foreign addresses (such as the envelope "from" address or
      originator header fields) may lead to inconsistent or incorrect

   The ":user" argument specifies that the user sub-part of the local-part which of
   an address.  Whether the user sub-part lies to the left or right of
   the separator character (e.g., "ken" in
   ""). sequence is dependent on the encompassing
   mail system.  If no separator character sequence exists, then ":user"
   specifies the entire left-side of the address (equivalent to

   The ":detail" argument specifies that the detail sub-part of the local-part
   which local-
   part of an address.  Whether the detail sub-part lies to the left or
   right of the separator character (e.g., "sieve" in
   ""). sequence is dependent on the
   encompassing mail system.  If no separator character sequence exists,
   the test evaluates to false.  If nothing lies to the right of the separator
   character, character sequence
   exists, but not detail information is provided, then ":detail" ":is"
   the null empty key ("").  Otherwise, the ":detail" sub-part contains ":contains"
   the null empty key.

      NOTE: If the separator character sequence occurs more than once in
      the local-part, then the address MUST be split at the left-most
      separator when the detail information is a suffix and at the
      right-most separator when the detail information is a prefix.

   Implementations MUST make sure that the separator character matches sequence
   and the ordering of the user and detail sub-parts match those that which is
   are used and/or allowed by the encompassing mail system, otherwise
   unexpected results might occur.  Implementations SHOULD allow the
   separator character sequence and sub-part ordering to be configurable
   so that they may be used with a variety of mail systems.  Note that
   the mechanisms used to define and/or query the separator character
   sequence and sub-part ordering used by the mail system are outside
   the scope of this document.

   The ":user" and ":detail" address parts are subject to the same rules
   and restrictions as the standard address parts defined in [RFC3028]. [I-D.ietf-

   For convenience, the "ADDRESS-PART" syntax element defined in
   [I-D.ietf-sieve-3028bis] is augmented here as follows:

         ADDRESS-PART  =/  ":user" / ":detail"

   A diagram showing the ADDRESS-PARTs of a email address utilizing where the
   detail information follows a separator character sequence of '+' "+" is
   shown below:

          :user "+" :detail  "@" :domain


   A diagram showing the ADDRESS-PARTs of a email address where the
   detail information precedes a separator character sequence of "--" is
   shown below:

          :detail "--" :user  "@" :domain
   Example (where the detail information follows "+"):

      require "subaddress";

      # File mailing list messages (subscribed as "ken+mta-filters").
      if envelope :detail "to" "mta-filters" {
        fileinto "inbox.ietf-mta-filters";

      # If a message is not directly to me (ignoring +detail), junk it.
      if not allof (address :user ["to", "cc", "bcc"] "cc"] "ken",
           address :domain ["to", "cc", "bcc"] "cc"] "") {

      # Redirect all mail sent to +foo.
      if envelope :detail "to" "foo" {
        redirect "";

4.  IANA Considerations

   This document requests that the IANA update the entry for the
   "subaddress" Sieve extension to point at this document.

5.  Security Considerations

   Security considerations are discussed in [RFC3028]. [I-D.ietf-sieve-3028bis].
   It is believed that this extension does not introduce any additional
   security concerns.

6.  Normative References

              Showalter, T. and P. Guenther, "Sieve: An Email Filtering
              Language", draft-ietf-sieve-3028bis-04 (work in progress),
              July 2005.

   [RFC2119]  Bradner, S., "Key words for use in RFCs to Indicate
              Requirement Levels", BCP 14, RFC 2119, March 1997.

   [RFC2822]  Resnick, P., "Internet Message Format", RFC 2822,
              April 2001.

   [RFC3028]  Showalter, T., "Sieve: A Mail Filtering Language",
              RFC 3028, January 2001.

Author's Address

   Kenneth Murchison
   Oceana Matrix Ltd.
   21 Princeton Place
   Orchard Park, NY  14127

   Phone: +1 716 662 8973

Appendix A.  Acknowledgments

   Thanks to Tim Showalter, Alexey Melnikov, Michael Salmon, Randall
   Gellens, Philip Guenther and Jutta Degener for their help with this

Appendix B.  Changes since RFC3598

   o  Allow detail information to be either or prefix or suffix to the

   o  Allow boundary between user and detail parts to be multiple

   o  Added note regarding processing of local-part with multiple
      separator characters. character sequences.

   o  Fixed envelope test example to only use "to" address.

   o  Refer to the zero-length string ("") as "empty" instead of "null"
      (per draft-ietf-sieve-3028bis)

   o  Miscellaneous editorial changes.

Author's Address

   Kenneth Murchison
   Oceana Matrix Ltd.
   2495 Main St.
   Suite 401
   Buffalo, NY  14214

   Phone: +1 716 604 0088

Intellectual Property Statement

   The IETF takes no position regarding the validity or scope of any
   Intellectual Property Rights or other rights that might be claimed to
   pertain to the implementation or use of the technology described in
   this document or the extent to which any license under such rights
   might or might not be available; nor does it represent that it has
   made any independent effort to identify any such rights.  Information
   on the procedures with respect to rights in RFC documents can be
   found in BCP 78 and BCP 79.

   Copies of IPR disclosures made to the IETF Secretariat and any
   assurances of licenses to be made available, or the result of an
   attempt made to obtain a general license or permission for the use of
   such proprietary rights by implementers or users of this
   specification can be obtained from the IETF on-line IPR repository at

   The IETF invites any interested party to bring to its attention any
   copyrights, patents or patent applications, or other proprietary
   rights that may cover technology that may be required to implement
   this standard.  Please address the information to the IETF at

Disclaimer of Validity

   This document and the information contained herein are provided on an

Copyright Statement

   Copyright (C) The Internet Society (2005).  This document is subject
   to the rights, licenses and restrictions contained in BCP 78, and
   except as set forth therein, the authors retain all their rights.


   Funding for the RFC Editor function is currently provided by the
   Internet Society.