draft-ietf-sieve-notify-mailto-00.txt   draft-ietf-sieve-notify-mailto-01.txt 
Sieve Working Group B. Leiba Sieve Working Group B. Leiba
Internet-Draft IBM T.J. Watson Research Center Internet-Draft IBM T.J. Watson Research Center
Expires: June 10, 2006 M. Haardt Expires: April 19, 2007 M. Haardt
freenet.de AG freenet.de AG
December 7, 2005 October 16, 2006
Sieve Notification Mechanism: mailto Sieve Notification Mechanism: mailto
draft-ietf-sieve-notify-mailto-00 draft-ietf-sieve-notify-mailto-01
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware 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 becomes have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79. aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
skipping to change at page 1, line 35 skipping to change at page 1, line 35
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on June 10, 2006. This Internet-Draft will expire on April 19, 2007.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2005). Copyright (C) The Internet Society (2006).
Abstract Abstract
This document describes a profile of the Sieve extension for This document describes a profile of the Sieve extension for
notifications, to allow notifications to be sent by electronic mail. notifications, to allow notifications to be sent by electronic mail.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 1.1. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.2 Conventions used in this document . . . . . . . . . . . . . . 3 1.2. Conventions used in this document . . . . . . . . . . . . . 3
2. Definition . . . . . . . . . . . . . . . . . . . . . . . . . . 4
2.1 Notify tag ":method" . . . . . . . . . . . . . . . . . . . . . 4
2.2 Notify tag ":id" . . . . . . . . . . . . . . . . . . . . . . . 4
2.3 Notify tag ":priority" . . . . . . . . . . . . . . . . . . . . 4
2.4 Notify tag ":message" . . . . . . . . . . . . . . . . . . . . 4
2.5 Other Definitions . . . . . . . . . . . . . . . . . . . . . . 5
3. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 2. Definition . . . . . . . . . . . . . . . . . . . . . . . . . 4
2.1. Notify tag ":method" . . . . . . . . . . . . . . . . . . . . 4
2.2. Notify tag ":priority" . . . . . . . . . . . . . . . . . . . 4
2.3. Notify tag ":message" . . . . . . . . . . . . . . . . . . . 4
2.4. Other Definitions . . . . . . . . . . . . . . . . . . . . . 5
4. Internationalization Considerations . . . . . . . . . . . . . 8 3. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 7
5. Security Considerations . . . . . . . . . . . . . . . . . . . 9 4. Internationalization Considerations . . . . . . . . . . . . 9
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10 5. Security Considerations . . . . . . . . . . . . . . . . . . 10
7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 11 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . 11
7.1 Normative References . . . . . . . . . . . . . . . . . . . . . 11
7.2 Non-Normative References . . . . . . . . . . . . . . . . . . . 11
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 11 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 12
7.1. Normative References . . . . . . . . . . . . . . . . . . . . 12
7.2. Non-Normative References . . . . . . . . . . . . . . . . . . 12
Intellectual Property and Copyright Statements . . . . . . . . 13 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . 13
Intellectual Property and Copyright Statements . . . . . . . 14
1. Introduction 1. Introduction
1.1 Overview 1.1. Overview
The [Notify] extension to the [Sieve] mail filtering language is a The [Notify] extension to the [Sieve] mail filtering language is a
framework for providing notifications by employing URIs to specify framework for providing notifications by employing URIs to specify
the notification mechanism. This document defines how [mailto] URIs the notification mechanism. This document defines how [mailto] URIs
are used to generate notifications by e-mail. are used to generate notifications by e-mail.
1.2 Conventions used in this document 1.2. Conventions used in this document
Conventions for notations are as in [Sieve] section 1.1, including Conventions for notations are as in [Sieve] section 1.1, including
the use of [Kwds] and the use of [ABNF]. the use of [Kwds] and the use of [ABNF].
[[no abnf ref: We don't actually need the ABNF reference...]] [[no abnf ref: We don't actually need the ABNF reference...]]
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [Kwds]. document are to be interpreted as described in [Kwds].
2. Definition 2. Definition
The mailto mechanism results in the sending of a new email message (a The mailto mechanism results in the sending of a new email message (a
"notification message") to notify a recipient about a "triggering "notification message") to notify a recipient about a "triggering
message". message".
2.1 Notify tag ":method" 2.1. Notify tag ":method"
The mailto notification mechanism uses standard mailto URIs as The mailto notification mechanism uses standard mailto URIs as
specified in [mailto]. URI parameters with hname "from", "subject" specified in [mailto]. URI headers with hname "from", "subject" and
and "received" are ignored if specified; all other parameters are "received" are ignored if specified; all other URI headers are
accepted. accepted.
[[Barry ignored: Should we ignore them, or should their presence be [[Barry ignored: Should we ignore them, or should their presence be
an error?]] an error?]]
2.2 Notify tag ":id" [[Michael ignored: The mailto URI spec allows for either. I like
ignoring them more, because it fits into the picture of ignoring a
The :id tag has no special meaning for this notification mechanism, different sender for other message-generating actions, if it is
and this specification puts no restriction on its use. forbidden.]]
2.3 Notify tag ":priority" 2.2. Notify tag ":priority"
The :priority tag has no special meaning for this notification The :priority tag has no special meaning for this notification
mechanism, and this specification puts no restriction on its use. mechanism, and this specification puts no restriction on its use.
Implementations MAY use the value of :priority to set a priority or Implementations MAY use the value of :priority to set a priority or
importance indication on the notification message. importance indication on the notification message.
2.4 Notify tag ":message" 2.3. Notify tag ":message"
o The "From:" header field and the envelope sender of the o Unless overridden by ":from", the "From:" header field and the
notification message are set to the envelope "to" field from the envelope sender of the notification message are set to the
triggering message, as used by Sieve. envelope "to" field from the triggering message, as used by Sieve.
[[Barry from: It might be better in some cases for the [[Barry from: It might be better in some cases for the
notification to "come from" the sender of the triggering message. notification to "come from" the sender of the triggering message.
In other cases it might be better for all notifications to come In other cases it might be better for all notifications to come
from the "mail system". I think we should define a way to specify from the "mail system". I think we should define a way to specify
the behaviour here, perhaps with a new notify tag.]] the behaviour here, perhaps with a new notify tag.]]
[[Michael from: Variables could perform both. Does that
suffice?]]
[[Barry sender: Should we also provide a mapping or setting for [[Barry sender: Should we also provide a mapping or setting for
the "Sender:" header field?]] the "Sender:" header field?]]
[[Michael sender: If that is required, the base spec should allow
it for all methods, like it offers ":from".]]
o The "To:" header field and the envelope recipient(s) of the o The "To:" header field and the envelope recipient(s) of the
notification message are set to the address(es) specified in URI notification message are set to the address(es) specified in URI
(including any URI parameters where the hname is "to"). (including any URI headers where the hname is "to").
[[Barry to: I'd like some way to specify that the To: header [[Barry to: I'd like some way to specify that the To: header
should be retained from the triggering message. In fact, I'd like should be retained from the triggering message. In fact, I'd like
a way to say that ALL headers be retained.]] a way to say that ALL headers be retained.]]
o The "Received:" headers from the triggering message are retained [[Michael to: Retaining the original "To:" field could easily
in the notification message, as these may help detect and prevent result in a loop. I think we need to define the focus of this
method: Generic SMTP message generation, or "just notifications"
over SMTP?]]
o The "Received:" field from the triggering message are retained in
the notification message, as these may help detect and prevent
mail loops. mail loops.
o The "Subject:" header of the notification message contains the o The "Subject:" field of the notification message contains the
value defined by the :message notify tag, as described in value defined by the :message notify tag, as described in
[Notify]. If there is no :message tag, the subject is retained [Notify]. If there is no :message tag, the subject is retained
from the triggering message. Note that Sieve variables can be from the triggering message. Note that Sieve [Variables] can be
used to advantage here, as shown in the example in Section 3. used to advantage here, as shown in the example in Section 3.
o All other header fields of the notification message either are as o All other header fields of the notification message either are as
specified in the URI, or have implementation-specific values; specified by URI headers, or have implementation-specific values;
their values are not defined here. their values are not defined here. It is suggested that the
implementation capitalizes the first letter of URI headers and
adds a space character after the colon between the mail header
name and value when adding URI headers to the message.
o If the mailto URI contains a "body" parameter, the value of that o If the mailto URI contains a "body" header, the value of that
parameter is used as the body of the notification message. If header is used as the body of the notification message. If there
there is no "body" parameter, the body of the notification message is no "body" header, the body of the notification message is
is empty. empty.
[[Barry body: I'd like some way to specify that the body contain [[Barry body: I'd like some way to specify that the body contain
the body of the triggering message.]] the body of the triggering message.]]
2.5 Other Definitions [[Michael body: Can variables do that? I don't know.]]
2.4. Other Definitions
Because the receipt of an email message is generating another email Because the receipt of an email message is generating another email
message, implementations MUST take steps to avoid mail loops. message, implementations MUST take steps to avoid mail loops. The
notification message contains the "Received:" fields from the
triggering message to allow loop detection as described in [RFC2821],
section 6.2. The implementation MUST allow messages with empty
envelope senders to trigger notifications.
[[Barry loops: We should say more about this...]] [[Barry loops: We should say more about this...]]
[[Michael loops: Ok now? Informal reference or normative? Could you
add it?]]
[[comment 1: Mailto URIs focus on the message, not its submission. [[comment 1: Mailto URIs focus on the message, not its submission.
There is no way to specify envelope parameters, require encryption or There is no way to specify envelope parameters, require encryption or
authentication. Sure enough there is more than SMTP, so mailto is authentication. Sure enough there is more than SMTP, so mailto is
fine not to address this specific transport, but should we ever need fine not to address this specific transport, but should we ever need
more, it can not be specified as URI parameter, because there is no more, it can not be specified as URI header, because there is no room
room in its namespace.]] in its namespace.]]
[[comment 2: Michael tried to get documentation on SMTP-SMS gateways, [[comment 2: Michael tried to get documentation on SMTP-SMS gateways,
but everybody operating one keeps the specification like a precious but everybody operating one keeps the specification like a precious
secret. From experiments made some years ago, we know some gateways secret. From experiments made some years ago, we know some gateways
ignore all messages with empty envelope senders, some do not ignore all messages with empty envelope senders, some do not
implement MIME and some ignore the body. Using empty envelope implement MIME and some ignore the body.]]
senders to avoid loops is not possible and it would not allow to send
notifications about bounces.]]
3. Examples 3. Examples
Triggering message (received by recipient@example.org): Triggering message (received by recipient@example.org):
Return-Path: <knitting-bounces@example.com> Return-Path: <knitting-bounces@example.com>
Received: from mail.example.com by mail.example.org Received: from mail.example.com by mail.example.org
for <recipient@example.org>; Wed, 7 Dec 2005 05:08:02 -0500 for <recipient@example.org>; Wed, 7 Dec 2005 05:08:02 -0500
Received: from hobbies.example.com by mail.example.com Received: from hobbies.example.com by mail.example.com
for <knitting@example.com>; Wed, 7 Dec 2005 02:00:26 -0800 for <knitting@example.com>; Wed, 7 Dec 2005 02:00:26 -0800
skipping to change at page 7, line 6 skipping to change at page 8, line 6
for <recipient@example.org>; Wed, 7 Dec 2005 05:08:02 -0500 for <recipient@example.org>; Wed, 7 Dec 2005 05:08:02 -0500
Received: from hobbies.example.com by mail.example.com Received: from hobbies.example.com by mail.example.com
for <knitting@example.com>; Wed, 7 Dec 2005 02:00:26 -0800 for <knitting@example.com>; Wed, 7 Dec 2005 02:00:26 -0800
Date: Wed, 7 Dec 2005 05:08:55 -0500 Date: Wed, 7 Dec 2005 05:08:55 -0500
Message-ID: <A2299BB.FF7788@example.org> Message-ID: <A2299BB.FF7788@example.org>
From: <recipient@example.org> From: <recipient@example.org>
To: <0123456789@sms.example.net> To: <0123456789@sms.example.net>
Subject: From Knitting list: A new sweater Subject: From Knitting list: A new sweater
Note that: Note that:
o Fields such as "Message-ID" and "Date" were generated afresh for o Fields such as "Message-ID:" and "Date:" were generated afresh for
the notification message, and do not relate to the triggering the notification message, and do not relate to the triggering
message. message.
o Additional "Received:" headers will be added to the notification o Additional "Received:" fields will be added to the notification
message in transit; the ones shown were copied from the triggering message in transit; the ones shown were copied from the triggering
message. message.
o If this message should appear at the mail.example.org server o If this message should appear at the mail.example.org server
again, the server can use the presence of a "mail.example.org" again, the server can use the presence of a "mail.example.org"
received line to avoid sending another notification. received line to avoid sending another notification.
4. Internationalization Considerations 4. Internationalization Considerations
[[Internationalization: What do we say here?]] [[Internationalization: What do we say here?]]
skipping to change at page 10, line 19 skipping to change at page 11, line 19
The following template specifies the IANA registration of the Sieve The following template specifies the IANA registration of the Sieve
notification mechanism specified in this document: notification mechanism specified in this document:
To: iana@iana.org To: iana@iana.org
Subject: Registration of new Sieve notification mechanism Subject: Registration of new Sieve notification mechanism
Mechanism name: mailto Mechanism name: mailto
Mechanism URI: draft-duerst-mailto-bis (change to RFC----) Mechanism URI: draft-duerst-mailto-bis (change to RFC----)
Mechanism-specific tags: none Mechanism-specific tags: none
Standards Track/IESG-approved experimental RFC number: this RFC Standards Track/IESG-approved experimental RFC number: this RFC
Person and email address to contact for further information: Person and email address to contact for further information:
Michael Haardt <michael@freenet-ag.de> Michael Haardt <michael.haardt@freenet-ag.de>
This information should be added to the list of sieve notification This information should be added to the list of sieve notification
mechanisms given on mechanisms given on
http://www.iana.org/assignments/sieve-notification. http://www.iana.org/assignments/sieve-notification.
7. References 7. References
7.1 Normative References 7.1. Normative References
[Kwds] Bradner, S., "Key words for use in RFCs to Indicate [Kwds] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", RFC 2119, March 1997. Requirement Levels", RFC 2119, March 1997.
[Notify] Melnikov, A., Ed., Leiba, B., Ed., Segmuller, W., and T. [Notify] Melnikov, A., Ed., Leiba, B., Ed., Segmuller, W., and T.
Martin, "Sieve Extension: Notifications", work in Martin, "Sieve Extension: Notifications", work in
progress, draft-ietf-sieve-notify, December 2005. progress, draft-ietf-sieve-notify, December 2005.
[Sieve] Guenther, P., Ed. and T. Showalter, Ed., "Sieve: An Email [Sieve] Guenther, P., Ed. and T. Showalter, Ed., "Sieve: An Email
Filtering Language", work in Filtering Language", work in
progress, draft-ietf-sieve-3028bis, November 2005. progress, draft-ietf-sieve-3028bis, November 2005.
[mailto] Duerst, M., Masinter, L., and J. Zawinski, "The mailto URI [mailto] Duerst, M., Masinter, L., and J. Zawinski, "The mailto URI
scheme", work in progress, draft-duerst-mailto-bis, scheme", work in progress, draft-duerst-mailto-bis,
February 2005. February 2005.
7.2 Non-Normative References 7.2. Non-Normative References
[ABNF] Crocker, D., Ed. and P. Overell, "Augmented BNF for Syntax [ABNF] Crocker, D., Ed. and P. Overell, "Augmented BNF for Syntax
Specifications: ABNF", RFC 4234, October 2005. Specifications: ABNF", RFC 4234, October 2005.
[RFC2821] Klensin, J., Ed., "Simple Mail Transfer Protocol",
RFC 2821, April 2001.
[Variables] [Variables]
Homme, K., "Sieve Extension: Variables", work in Homme, K., "Sieve Extension: Variables", work in
progress, draft-ietf-sieve-variables, October 2005. progress, draft-ietf-sieve-variables, October 2005.
Authors' Addresses Authors' Addresses
Barry Leiba Barry Leiba
IBM T.J. Watson Research Center IBM T.J. Watson Research Center
19 Skyline Drive 19 Skyline Drive
Hawthorne, NY 10532 Hawthorne, NY 10532
skipping to change at page 12, line 4 skipping to change at page 13, line 15
Authors' Addresses Authors' Addresses
Barry Leiba Barry Leiba
IBM T.J. Watson Research Center IBM T.J. Watson Research Center
19 Skyline Drive 19 Skyline Drive
Hawthorne, NY 10532 Hawthorne, NY 10532
US US
Phone: +1 914 784 7941 Phone: +1 914 784 7941
Email: leiba@watson.ibm.com Email: leiba@watson.ibm.com
Michael Haardt Michael Haardt
freenet.de AG freenet.de AG
Willstaetter Str. 13 Willstaetter Str. 13
Duesseldorf, NRW 40549 Duesseldorf, NRW 40549
Germany Germany
Phone: +49 241 53087 520 Phone: +49 241 53087 520
Email: michael.haardt@freenet-ag.de Email: michael.haardt@freenet-ag.de
Intellectual Property Statement Full Copyright Statement
Copyright (C) The Internet Society (2006).
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.
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Intellectual Property
The IETF takes no position regarding the validity or scope of any The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights 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 might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be on the procedures with respect to rights in RFC documents can be
found in BCP 78 and BCP 79. found in BCP 78 and BCP 79.
skipping to change at page 13, line 29 skipping to change at page 14, line 45
such proprietary rights by implementers or users of this such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr. http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at this standard. Please address the information to the IETF at
ietf-ipr@ietf.org. ietf-ipr@ietf.org.
Disclaimer of Validity
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
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.
Acknowledgment Acknowledgment
Funding for the RFC Editor function is currently provided by the Funding for the RFC Editor function is currently provided by the
Internet Society. Internet Society.
 End of changes. 43 change blocks. 
78 lines changed or deleted 100 lines changed or added

This html diff was produced by rfcdiff 1.33. The latest version is available from http://tools.ietf.org/tools/rfcdiff/