draft-ietf-sieve-notify-mailto-02.txt   draft-ietf-sieve-notify-mailto-03.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
Intended status: Standards Track M. Haardt Intended status: Standards Track M. Haardt
Expires: September 8, 2007 freenet.de AG Expires: January 7, 2008 freenet AG
March 7, 2007 July 6, 2007
Sieve Notification Mechanism: mailto Sieve Notification Mechanism: mailto
draft-ietf-sieve-notify-mailto-02 draft-ietf-sieve-notify-mailto-03
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 September 8, 2007. This Internet-Draft will expire on January 7, 2008.
Copyright Notice Copyright Notice
Copyright (C) The IETF Trust (2007). Copyright (C) The IETF Trust (2007).
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. Definition . . . . . . . . . . . . . . . . . . . . . . . . . 4
2.1. Notify tag ":method" . . . . . . . . . . . . . . . . . . . . 4 2.1. Notify parameter "method" . . . . . . . . . . . . . . . . . 4
2.2. Notify tag ":importance" . . . . . . . . . . . . . . . . . . 4 2.2. Notify tag ":from" . . . . . . . . . . . . . . . . . . . . . 4
2.3. Notify tag ":message" . . . . . . . . . . . . . . . . . . . 4 2.3. Notify tag ":importance" . . . . . . . . . . . . . . . . . . 4
2.4. Other Definitions . . . . . . . . . . . . . . . . . . . . . 5 2.4. Notify tag ":options" . . . . . . . . . . . . . . . . . . . 4
2.5. Notify tag ":message" . . . . . . . . . . . . . . . . . . . 4
2.6. Other Definitions . . . . . . . . . . . . . . . . . . . . . 5
3. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 6 3. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 6
4. Internationalization Considerations . . . . . . . . . . . . 8 4. Internationalization Considerations . . . . . . . . . . . . 8
5. Security Considerations . . . . . . . . . . . . . . . . . . 9 5. Security Considerations . . . . . . . . . . . . . . . . . . 9
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . 10 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . 10
7. References . . . . . . . . . . . . . . . . . . . . . . . . . 11 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 11
skipping to change at page 4, line 11 skipping to change at page 4, line 11
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 parameter "method"
The mailto notification mechanism uses standard mailto URIs as The mailto notification mechanism uses standard mailto URIs as
specified in [mailto]. URI headers with hname "from", "subject" and specified in [mailto].
"received" are ignored if specified; all other URI headers are
accepted.
[[Barry ignored: Should we ignore them, or should their presence be
an error?]]
[[Michael ignored: The mailto URI spec allows for either. I like 2.2. Notify tag ":from"
ignoring them more, because it fits into the picture of ignoring a
different sender for other message-generating actions, if it is
forbidden.]]
[[Barry ignored 2: My thinking, when I suggested error, was that a The :from tag overrides the default sender of the notification
script that explicitly tried to use them, even when this spec says message.
"don't", would be broken. I see no reasonable scenario through which
the mailto URI could be derived in a computed way that would include
those fields, and thus justify ignoring them rather than considering
them an error.]]
2.2. Notify tag ":importance" 2.3. Notify tag ":importance"
The :importance tag has no special meaning for this notification The :importance 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 :importance to set a priority or Implementations MAY use the value of :importance to set a priority or
importance indication on the notification message. importance indication on the notification message.
2.3. Notify tag ":message" 2.4. Notify tag ":options"
This tag is not used by the mailto method.
2.5. Notify tag ":message"
o Unless overridden by ":from", the "From:" header field and the o Unless overridden by ":from", the "From:" header field and the
envelope sender of the notification message are set either to the envelope sender of the notification message are set either to the
envelope "to" field from the triggering message, as used by Sieve, envelope "to" field from the triggering message, as used by Sieve,
or to a fixed address (so it "comes from the notification or to a fixed address (so it "comes from the notification
system"), at the discretion of the implementation. system"), at the discretion of the implementation.
[[Barry sender: Alternative: the "from" is set to the envelope to,
and the "sender" is set to the adderss of the notification
system?]]
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 headers where the hname is "to"). (including any URI headers where the hname is "to").
o The "Received:" field from the triggering message are retained in o The "Received:" field from the triggering message are retained in
the notification message, as these may help detect and prevent the notification message, as these may help detect and prevent
mail loops. mail loops.
o The "Subject:" field 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 If the mailto URI contains a "body" header, the value of that
header is used as the body of the notification message. If there
is no "body" header, it is up to the implementation to leave the
body empty or use an excerpt of the original message.
o URI headers with hname "received" are considered unsafe and are
ignored if specified. URI headers with hname "from" and "subject"
conflict with the implictly set values from and are ignored if
specified.
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 by URI headers, or have implementation-specific values; specified by URI headers, or have implementation-specific values;
their values are not defined here. It is suggested that the their values are not defined here. It is suggested that the
implementation capitalizes the first letter of URI headers and implementation capitalizes the first letter of URI headers and
adds a space character after the colon between the mail header adds a space character after the colon between the mail header
name and value when adding URI headers to the message. name and value when adding URI headers to the message.
o If the mailto URI contains a "body" header, the value of that 2.6. Other Definitions
header is used as the body of the notification message. If there
is no "body" header, the body of the notification message is
empty.
[[Barry body: I'd like some way to specify that the body contain
some excerpt from the body of the triggering message. Does anyone
else want this, or should we just say "Barry's being silly," and
forget it?]]
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. The message, implementations MUST take steps to avoid mail loops. The
notification message contains the "Received:" fields from the notification message contains the "Received:" fields from the
triggering message to allow loop detection as described in [RFC2821], triggering message to allow loop detection as described in [RFC2821],
section 6.2. The implementation MUST allow messages with empty section 6.2. The implementation MUST allow messages with empty
envelope senders to trigger notifications. envelope senders to trigger notifications.
[[comment 1: Mailto URIs focus on the message, not its submission.
There is no way to specify envelope parameters, require encryption or
authentication. Sure enough there is more than SMTP, so mailto is
fine not to address this specific transport, but should we ever need
more, it can not be specified as URI header, because there is no room
in its namespace.]]
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
Message-ID: <1234567.89ABCDEF@example.com> Message-ID: <1234567.89ABCDEF@example.com>
skipping to change at page 6, line 32 skipping to change at page 6, line 32
Subject: [Knitting] A new sweater Subject: [Knitting] A new sweater
I just finished a great new sweater! I just finished a great new sweater!
Sieve script (run on behalf of recipient@example.org): Sieve script (run on behalf of recipient@example.org):
require ["notify", "variables"]; require ["notify", "variables"];
if header :contains "list-id" "knitting.example.com" { if header :contains "list-id" "knitting.example.com" {
if header :matches "Subject" "[*] *" { if header :matches "Subject" "[*] *" {
notify :method "mailto:0123456789@sms.example.net" notify :message "From ${1} list: ${2}"
:message "From ${1} list: ${2}" :importance "3"
:importance "3"; "mailto:0123456789@sms.example.net";
} }
} }
Notification message: Notification message:
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
Date: Wed, 7 Dec 2005 05:08:55 -0500 Date: Wed, 7 Dec 2005 05:08:55 -0500
skipping to change at page 8, line 7 skipping to change at page 8, line 7
o Additional "Received:" fields 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?]] This specification introduces no specific internationalization issues
that are not already addressed in [Sieve] and in [Notify].
5. Security Considerations 5. Security Considerations
Sending a notification is comparable with forwarding mail to the Sending a notification is comparable with forwarding mail to the
notification recipient. Care must be taken when forwarding mail notification recipient. Care must be taken when forwarding mail
automatically, to ensure that confidential information is not sent automatically, to ensure that confidential information is not sent
into an insecure environment. into an insecure environment.
The automated sending of email messages exposes the system to mail The automated sending of email messages exposes the system to mail
loops, which can cause operational problems. Implementations of this loops, which can cause operational problems. Implementations of this
specification MUST protect themselves against mail loops. specification MUST protect themselves against mail loops.
Additional security considerations are discussed in [Sieve] and in Additional security considerations are discussed in [Sieve] and in
[Notify]. [Notify].
6. IANA Considerations 6. IANA Considerations
[[IANA to-do: What do we need to do to actually get this set up with
IANA?]]
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: RFC2368
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.haardt@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
skipping to change at page 11, line 20 skipping to change at page 11, line 20
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] Hoffman, P., Masinter, L., and J. Zawinski, "The mailto
scheme", work in progress, draft-duerst-mailto-bis, URL scheme", RFC 2368, July 1998.
February 2005.
7.2. Non-Normative References 7.2. Non-Normative References
[RFC2821] Klensin, J., Ed., "Simple Mail Transfer Protocol", [RFC2821] Klensin, J., Ed., "Simple Mail Transfer Protocol",
RFC 2821, April 2001. 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.
skipping to change at page 12, line 17 skipping to change at page 12, line 17
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 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
Full Copyright Statement Full Copyright Statement
Copyright (C) The IETF Trust (2007). Copyright (C) The IETF Trust (2007).
This document is subject to the rights, licenses and restrictions This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors contained in BCP 78, and except as set forth therein, the authors
retain all their rights. retain all their rights.
This document and the information contained herein are provided on an This document and the information contained herein are provided on an
 End of changes. 21 change blocks. 
60 lines changed or deleted 42 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/