draft-ietf-sieve-notify-mailto-05.txt   draft-ietf-sieve-notify-mailto-06.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: April 7, 2008 freenet AG Expires: August 28, 2008 freenet AG
October 5, 2007 February 25, 2008
Sieve Notification Mechanism: mailto Sieve Notification Mechanism: mailto
draft-ietf-sieve-notify-mailto-05 draft-ietf-sieve-notify-mailto-06
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 April 7, 2008. This Internet-Draft will expire on August 28, 2008.
Copyright Notice Copyright Notice
Copyright (C) The IETF Trust (2007). Copyright (C) The IETF Trust (2008).
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
skipping to change at page 2, line 25 skipping to change at page 2, line 25
2. Definition . . . . . . . . . . . . . . . . . . . . . . . . . 4 2. Definition . . . . . . . . . . . . . . . . . . . . . . . . . 4
2.1. Notify parameter "method" . . . . . . . . . . . . . . . . . 4 2.1. Notify parameter "method" . . . . . . . . . . . . . . . . . 4
2.2. Test notify_method_capability . . . . . . . . . . . . . . . 4 2.2. Test notify_method_capability . . . . . . . . . . . . . . . 4
2.3. Notify tag ":from" . . . . . . . . . . . . . . . . . . . . . 4 2.3. Notify tag ":from" . . . . . . . . . . . . . . . . . . . . . 4
2.4. Notify tag ":importance" . . . . . . . . . . . . . . . . . . 4 2.4. Notify tag ":importance" . . . . . . . . . . . . . . . . . . 4
2.5. Notify tag ":options" . . . . . . . . . . . . . . . . . . . 4 2.5. Notify tag ":options" . . . . . . . . . . . . . . . . . . . 4
2.6. Notify tag ":message" . . . . . . . . . . . . . . . . . . . 4 2.6. Notify tag ":message" . . . . . . . . . . . . . . . . . . . 4
2.7. Other Definitions . . . . . . . . . . . . . . . . . . . . . 5 2.7. Other Definitions . . . . . . . . . . . . . . . . . . . . . 5
3. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 7 3. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 8
4. Internationalization Considerations . . . . . . . . . . . . 9 4. Internationalization Considerations . . . . . . . . . . . . 10
5. Security Considerations . . . . . . . . . . . . . . . . . . 10 5. Security Considerations . . . . . . . . . . . . . . . . . . 11
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . 11 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . 12
6.1. Registration of notification mechanism . . . . . . . . . . . 11 6.1. Registration of notification mechanism . . . . . . . . . . . 12
6.2. New registry for Auto-Submitted header field keywords . . . 11 6.2. New registry for Auto-Submitted header field keywords . . . 12
6.3. Initial registration of Auto-Submitted header field 6.3. Initial registration of Auto-Submitted header field
keywords . . . . . . . . . . . . . . . . . . . . . . . . . . 11 keywords . . . . . . . . . . . . . . . . . . . . . . . . . . 12
7. References . . . . . . . . . . . . . . . . . . . . . . . . . 13 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 14
7.1. Normative References . . . . . . . . . . . . . . . . . . . . 13 7.1. Normative References . . . . . . . . . . . . . . . . . . . . 14
7.2. Non-Normative References . . . . . . . . . . . . . . . . . . 13 7.2. Non-Normative References . . . . . . . . . . . . . . . . . . 14
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . 14 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . 15
Intellectual Property and Copyright Statements . . . . . . . 15 Intellectual Property and Copyright Statements . . . . . . . 16
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.
skipping to change at page 5, line 16 skipping to change at page 5, line 16
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 REQUIRED inclusion of an "Auto-Submitted:" field, section 6.2. The REQUIRED inclusion of an "Auto-Submitted:" field,
as described in the message composition guidelines, will also help in as described in the message composition guidelines, will also help in
loop detection and avoidance. loop detection and avoidance.
Implementations MUST NOT trigger notifications for messages Implementations MUST NOT trigger notifications for messages
containing "Auto-Submitted:" header fields. containing "Auto-Submitted:" header fields with any value other than
"No".
Implementations MUST allow messages with empty envelope senders to Implementations MUST allow messages with empty envelope senders to
trigger notifications. trigger notifications.
Because this notification method uses a store-and-forward system for Because this notification method uses a store-and-forward system for
delivery of the notification message, the Sieve processor should not delivery of the notification message, the Sieve processor should not
have a need to retry notifications. Therefore, implementations of have a need to retry notifications. Therefore, implementations of
this method SHOULD use normal mechanisms for submitting SMTP messages this method SHOULD use normal mechanisms for submitting SMTP messages
and for retrying the initial submission. Once the notification and for retrying the initial submission. Once the notification
message is submitted, implementations MUST NOT resubmit it, as this message is submitted, implementations MUST NOT resubmit it, as this
is likely to result in multiple notifications, and increases the is likely to result in multiple notifications, and increases the
danger of message loops. danger of message loops.
The overall notification message is composed using the following The overall notification message is composed using the following
guidelines (see [RFC2822] for references to message header fields): guidelines (see [RFC2822] for references to message header fields):
o If the envelope sender of the triggering message is empty, the
envelope sender of the notification message MUST be empty as well,
to avoid message loops. Otherwise, the envelope sender of the
notification message is set to the value of the ":from" parameter
to the notify action, if one is specified, has email address
syntax and is valid according to the implementation specific
security checks (see Section 3.3 of [Notify]). If ":from" is not
specified or is not valid, the envelope sender of the notification
message is set either to the envelope "to" field from the
triggering message, as used by Sieve, or to a fixed email address
(so it "comes from the notification system"), at the discretion of
the implementation. This may not be overridden by a "from" URI
header, and any such URI header MUST be ignored.
o The header field "Auto-Submitted: sieve-notify" MUST be included o The header field "Auto-Submitted: sieve-notify" MUST be included
in the notification message (see [RFC3834]). This is to reduce in the notification message (see [RFC3834]). This is to reduce
the likelihood of message loops, by tagging this as an the likelihood of message loops, by tagging this as an
automatically generated message. Among other results, it will automatically generated message. Among other results, it will
cause the notification message not to generate further cause the notification message not to generate further
notifications. notifications. mailto URI headers with hname "auto-submitted" are
considered unsafe and MUST be ignored.
o Unless overridden by ":from", the "From:" header field and the o The "From:" header field of the notification message is set to the
envelope sender of the notification message are set either to the value of the ":from" parameter to the notify action, if one is
envelope "to" field from the triggering message, as used by Sieve, specified, has email address syntax and is valid according to the
or to a fixed address (so it "comes from the notification implementation specific security checks (see Section 3.3 of
system"), at the discretion of the implementation. This may not [Notify]). If ":from" is not specified or is not valid, the
be overridden by a "from" URI header, and any such URI header will "From:" header field of the notification message is set either to
be ignored. the envelope "to" field from the triggering message, as used by
Sieve, or to a fixed email address (so it "comes from the
notification system"), at the discretion of the implementation.
This may not be overridden by a "from" URI header, and any such
URI header MUST be ignored.
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 the notification message are set to the address(es) specified in the
URI (including any URI headers where the hname is "to"). URI (including any URI headers where the hname is "to").
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 and there is a "subject" [Notify]. If there is no :message tag and there is a "subject"
header on the URI, then that value is used. If that is also header on the URI, then that value is used. If that is also
absent, the subject is retained from the triggering message. Note absent, the subject is retained from the triggering message. Note
skipping to change at page 15, line 7 skipping to change at page 16, line 7
freenet 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 Email: michael.haardt@freenet.ag
Full Copyright Statement Full Copyright Statement
Copyright (C) The IETF Trust (2007). Copyright (C) The IETF Trust (2008).
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
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
 End of changes. 16 change blocks. 
27 lines changed or deleted 47 lines changed or added

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