draft-ietf-sieve-vacation-06.txt   draft-ietf-sieve-vacation-07.txt 
SIEVE Email Filtering Working T. Showalter SIEVE Email Filtering Working T. Showalter
Group Group
Internet-Draft N. Freed, Ed. Internet-Draft N. Freed, Ed.
Expires: August 6, 2006 Sun Microsystems Expires: September 4, 2007 Sun Microsystems
February 2, 2006 March 3, 2007
Sieve Email Filtering: Vacation Extension Sieve Email Filtering: Vacation Extension
draft-ietf-sieve-vacation-06 draft-ietf-sieve-vacation-07
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 August 6, 2006. This Internet-Draft will expire on September 4, 2007.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2006). Copyright (C) The IETF Trust (2007).
Abstract Abstract
This document describes an extension to the Sieve email filtering This document describes an extension to the Sieve email filtering
language for an autoresponder similar to that of the Unix "vacation" language for an autoresponder similar to that of the Unix "vacation"
command for replying to messages. Various safety features are command for replying to messages. Various safety features are
included to prevent problems such as message loops. included to prevent problems such as message loops.
Change History (to be removed prior to publication as an RFC) Change History (to be removed prior to publication as an RFC)
Changes from draft-showalter-sieve-vacation-06.txt: Changes from draft-showalter-sieve-vacation-06.txt:
1. Updated to XML source. 1. Updated to XML source.
2. Added :from parameter. 2. Added :from parameter.
3. Added :handle parameter. 3. Added :handle parameter.
4. Added more detailed description of :subject parameter 4. Added more detailed description of :subject parameter
skipping to change at page 3, line 13 skipping to change at page 3, line 13
should be sent. (This just reiterates the advice in RFC 3834.) should be sent. (This just reiterates the advice in RFC 3834.)
19. Added an implementation note about how to construct a hash of 19. Added an implementation note about how to construct a hash of
vacation action parameters. vacation action parameters.
20. Clarified what to do when :subject isn't used and the original 20. Clarified what to do when :subject isn't used and the original
message also doesn't contain a Subject field. message also doesn't contain a Subject field.
21. Corrected typos, added Internationalization Considerations 21. Corrected typos, added Internationalization Considerations
section. section.
22. Updated IANA Considerations with new registrtion form
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4
2. Conventions used in this document . . . . . . . . . . . . . . 4 2. Conventions used in this document . . . . . . . . . . . . . . 4
3. Capability Identifier . . . . . . . . . . . . . . . . . . . . 4 3. Capability Identifier . . . . . . . . . . . . . . . . . . . . 4
4. Vacation Action . . . . . . . . . . . . . . . . . . . . . . . 4 4. Vacation Action . . . . . . . . . . . . . . . . . . . . . . . 4
4.1. Days Parameter . . . . . . . . . . . . . . . . . . . . . . 4 4.1. Days Parameter . . . . . . . . . . . . . . . . . . . . . . 4
4.2. Previous Response Tracking . . . . . . . . . . . . . . . . 5 4.2. Previous Response Tracking . . . . . . . . . . . . . . . . 5
4.3. Subject and from parameters . . . . . . . . . . . . . . . 7 4.3. Subject and From Parameters . . . . . . . . . . . . . . . 7
4.4. MIME Parameter . . . . . . . . . . . . . . . . . . . . . . 7 4.4. MIME Parameter . . . . . . . . . . . . . . . . . . . . . . 7
4.5. Address Parameter and Limiting Replies to Personal 4.5. Address Parameter and Limiting Replies to Personal
Messages . . . . . . . . . . . . . . . . . . . . . . . . . 8 Messages . . . . . . . . . . . . . . . . . . . . . . . . . 8
4.6. Restricting Replies to Automated Processes and Mailing 4.6. Restricting Replies to Automated Processes and Mailing
Lists . . . . . . . . . . . . . . . . . . . . . . . . . . 8 Lists . . . . . . . . . . . . . . . . . . . . . . . . . . 8
4.7. Interaction with Other Sieve Actions . . . . . . . . . . . 9 4.7. Interaction with Other Sieve Actions . . . . . . . . . . . 9
4.8. Examples . . . . . . . . . . . . . . . . . . . . . . . . . 9 4.8. Examples . . . . . . . . . . . . . . . . . . . . . . . . . 9
5. Response Message Generation . . . . . . . . . . . . . . . . . 10 5. Response Message Generation . . . . . . . . . . . . . . . . . 10
5.1. SMTP MAIL FROM address . . . . . . . . . . . . . . . . . . 10 5.1. SMTP MAIL FROM address . . . . . . . . . . . . . . . . . . 10
5.2. Date . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 5.2. Date . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
skipping to change at page 3, line 47 skipping to change at page 3, line 49
5.8. In-Reply-To and References . . . . . . . . . . . . . . . . 11 5.8. In-Reply-To and References . . . . . . . . . . . . . . . . 11
6. Relationship to Recommendations for Automatic Responses to 6. Relationship to Recommendations for Automatic Responses to
Electronic Mail . . . . . . . . . . . . . . . . . . . . . . . 11 Electronic Mail . . . . . . . . . . . . . . . . . . . . . . . 11
7. Internationalization Considerations . . . . . . . . . . . . . 11 7. Internationalization Considerations . . . . . . . . . . . . . 11
8. Security Considerations . . . . . . . . . . . . . . . . . . . 13 8. Security Considerations . . . . . . . . . . . . . . . . . . . 13
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13
10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 14 10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 14
10.1. Normative References . . . . . . . . . . . . . . . . . . . 14 10.1. Normative References . . . . . . . . . . . . . . . . . . . 14
10.2. Informative References . . . . . . . . . . . . . . . . . . 14 10.2. Informative References . . . . . . . . . . . . . . . . . . 14
Appendix A. Acknowledgements . . . . . . . . . . . . . . . . . . 15 Appendix A. Acknowledgements . . . . . . . . . . . . . . . . . . 15
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 16 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 15
Intellectual Property and Copyright Statements . . . . . . . . . . 17 Intellectual Property and Copyright Statements . . . . . . . . . . 16
1. Introduction 1. Introduction
This document defines an extension to the Sieve language defined in This document defines an extension to the Sieve language defined in
[I-D.ietf-sieve-3028bis] for notification that messages to a [I-D.ietf-sieve-3028bis] for notification that messages to a
particular recipient will not be answered immediately. particular recipient will not be answered immediately.
2. Conventions used in this document 2. Conventions used in this document
Conventions for notations are as in [I-D.ietf-sieve-3028bis] section Conventions for notations are as in [I-D.ietf-sieve-3028bis] section
skipping to change at page 7, line 19 skipping to change at page 7, line 19
value for different parameters produce the same hash value. One value for different parameters produce the same hash value. One
possible way to accomplish this apply the hash to a series of counted possible way to accomplish this apply the hash to a series of counted
or null terminated strings, one for each possible parameter in or null terminated strings, one for each possible parameter in
particular order. particular order.
Implementations are free to limit the number of remembered responses, Implementations are free to limit the number of remembered responses,
however, the limit MUST NOT be less than 1000. When limiting the however, the limit MUST NOT be less than 1000. When limiting the
number of tracked responses, implementations SHOULD discard the number of tracked responses, implementations SHOULD discard the
oldest ones first. oldest ones first.
4.3. Subject and from parameters 4.3. Subject and From Parameters
The ":subject" parameter specifies a subject line to attach to any The ":subject" parameter specifies a subject line to attach to any
vacation response that is generated. UTF-8 characters can be used in vacation response that is generated. UTF-8 characters can be used in
the string argument; implementations MUST convert the string to the string argument; implementations MUST convert the string to
[RFC2047] encoded words if and only if non-ASCII characters are [RFC2047] encoded words if and only if non-ASCII characters are
present. Implementations MUST generate an appropriate default present. Implementations MUST generate an appropriate default
subject line as specified below if no :subject parameter is subject line as specified below if no :subject parameter is
specified. specified.
A ":from" parameter may be used to specify an alternate address to A ":from" parameter may be used to specify an alternate address to
skipping to change at page 9, line 41 skipping to change at page 9, line 41
4.7. Interaction with Other Sieve Actions 4.7. Interaction with Other Sieve Actions
Vacation does not affect Sieve's implicit keep action. Vacation does not affect Sieve's implicit keep action.
Vacation can only be executed once per script. A script MUST fail Vacation can only be executed once per script. A script MUST fail
with an appropriate error if it attempts to execute two or more with an appropriate error if it attempts to execute two or more
vacation actions. vacation actions.
Implementations MUST NOT consider vacation used with discard, keep, Implementations MUST NOT consider vacation used with discard, keep,
fileinto, or redirect an error. The vacation action is incompatible fileinto, or redirect an error. The vacation action is incompatible
with the Sieve reject and refuse actions [I-D.ietf-sieve-refuse- with the Sieve reject and refuse actions
reject]. [I-D.ietf-sieve-refuse-reject].
4.8. Examples 4.8. Examples
Here is a simple use of vacation. Here is a simple use of vacation.
require "vacation"; require "vacation";
vacation :days 23 :addresses ["tjs@example.edu", vacation :days 23 :addresses ["tjs@example.edu",
"ts4z@landru.example.edu"] "ts4z@landru.example.edu"]
"I'm away until October 19. "I'm away until October 19.
skipping to change at page 12, line 16 skipping to change at page 12, line 16
internationalization issues raised by the use of the vacation internationalization issues raised by the use of the vacation
extension. extension.
Vacation messages are normally written using the UTF-8 charset, Vacation messages are normally written using the UTF-8 charset,
allowing text to be written in most of the world's languages. allowing text to be written in most of the world's languages.
Additionally, the :mime parameter allows specification of arbitrary Additionally, the :mime parameter allows specification of arbitrary
MIME content. In particular, this makes it possible to use MIME content. In particular, this makes it possible to use
multipart/alternative objects to specify vacation responses in multipart/alternative objects to specify vacation responses in
multiple languages simultaneously. multiple languages simultaneously.
The Sieve language itself allows a vacation response to selected The Sieve language itself allows a vacation response to be selected
based on the content of the original message. For example, the based on the content of the original message. For example, the
Accept-Language or Content-Language header fields [RFC3282] could be Accept-Language or Content-Language header fields [RFC3282] could be
checked and used to select appropriate text: checked and used to select appropriate text:
require "vacation"; require "vacation";
if header :contains ["accept-language", "content-language"] "en" if header :contains ["accept-language", "content-language"] "en"
{ {
vacation "I am away this week."; vacation "I am away this week.";
} else { } else {
vacation "Estoy ausente esta semana."; vacation "Estoy ausente esta semana.";
skipping to change at page 13, line 38 skipping to change at page 13, line 38
9. IANA Considerations 9. IANA Considerations
The following template specifies the IANA registration of the The following template specifies the IANA registration of the
vacation Sieve extension specified in this document: vacation Sieve extension specified in this document:
To: iana@iana.org To: iana@iana.org
Subject: Registration of new Sieve extension Subject: Registration of new Sieve extension
Capability name: vacation Capability name: vacation
Capability keyword: vacation Description: This document describes a Sieve extension for
Capability arguments: N/A an autoresponder similar to that of the Unix
Standards Track/IESG-approved experimental RFC number: this RFC "vacation" command for replying to messages.
Person and email address to contact for further information: RFC number: RFC XXXX
Ned Freed Contact address: Ned Freed <ned.freed@mrochek.com>
E-Mail: ned.freed@mrochek.com
This information should be added to the list of Sieve extensions This information should be added to the list of Sieve extensions
given on http://www.iana.org/assignments/sieve-extensions. given on http://www.iana.org/assignments/sieve-extensions.
10. References 10. References
10.1. Normative References 10.1. Normative References
[I-D.ietf-sieve-3028bis] [I-D.ietf-sieve-3028bis]
Guenther, P. and T. Showalter, "Sieve: An Email Filtering Guenther, P. and T. Showalter, "Sieve: An Email Filtering
Language", draft-ietf-sieve-3028bis-04 (work in progress), Language", draft-ietf-sieve-3028bis-12 (work in progress),
July 2005, <http://www.ietf.org/internet-drafts/ February 2007, <http://www.ietf.org/internet-drafts/
draft-ietf-sieve-3028bis-04.txt>. draft-ietf-sieve-3028bis-12.txt>.
[I-D.ietf-sieve-variables] [I-D.ietf-sieve-variables]
Homme, K., "Sieve Mail Filtering Language: Variables Homme, K., "Sieve Mail Filtering Language: Variables
Extension", draft-ietf-sieve-variables-04 (work in Extension", draft-ietf-sieve-variables-08 (work in
progress), July 2005, <http://www.ietf.org/ progress), December 2005, <http://www.ietf.org/
internet-drafts/draft-ietf-sieve-variables-04.txt>. internet-drafts/draft-ietf-sieve-variables-08.txt>.
[RFC2045] Freed, N. and N. Borenstein, "Multipurpose Internet Mail [RFC2045] Freed, N. and N. Borenstein, "Multipurpose Internet Mail
Extensions (MIME) Part One: Format of Internet Message Extensions (MIME) Part One: Format of Internet Message
Bodies", RFC 2045, November 1996. Bodies", RFC 2045, November 1996.
[RFC2047] Moore, K., "MIME (Multipurpose Internet Mail Extensions) [RFC2047] Moore, K., "MIME (Multipurpose Internet Mail Extensions)
Part Three: Message Header Extensions for Non-ASCII Text", Part Three: Message Header Extensions for Non-ASCII Text",
RFC 2047, November 1996. RFC 2047, November 1996.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
skipping to change at page 17, line 5 skipping to change at page 16, line 5
Ned Freed (editor) Ned Freed (editor)
Sun Microsystems Sun Microsystems
3401 Centrelake Drive, Suite 410 3401 Centrelake Drive, Suite 410
Ontario, CA 92761-1205 Ontario, CA 92761-1205
USA USA
Phone: +1 909 457 4293 Phone: +1 909 457 4293
Email: ned.freed@mrochek.com Email: ned.freed@mrochek.com
Intellectual Property Statement Full Copyright Statement
Copyright (C) The IETF Trust (2007).
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, THE IETF TRUST 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 17, line 29 skipping to change at page 16, 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 (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.
Acknowledgment Acknowledgment
Funding for the RFC Editor function is currently provided by the Funding for the RFC Editor function is provided by the IETF
Internet Society. Administrative Support Activity (IASA).
 End of changes. 17 change blocks. 
41 lines changed or deleted 43 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/