draft-ietf-sieve-vacation-03.txt   draft-ietf-sieve-vacation-04.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: March 25, 2006 Sun Microsystems Expires: April 14, 2006 Sun Microsystems
September 21, 2005 October 11, 2005
Sieve Email Filtering: Vacation Extension Sieve Email Filtering: Vacation Extension
draft-ietf-sieve-vacation-03 draft-ietf-sieve-vacation-04
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 March 25, 2006. This Internet-Draft will expire on April 14, 2006.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2005). Copyright (C) The Internet Society (2005).
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
skipping to change at page 3, line 5 skipping to change at page 2, line 40
12. Switched Syntax: label to Usage: 12. Switched Syntax: label to Usage:
13. Updated draft to refer to RFC 3028bis instead of RFC 3028. 13. Updated draft to refer to RFC 3028bis instead of RFC 3028.
14. Removed reference to section 2.4.2.4 of RFC 3028 since the 14. Removed reference to section 2.4.2.4 of RFC 3028 since the
section no longer exists in the revised version. section no longer exists in the revised version.
15. Updated reference for sieve reject, added text about refuse. 15. Updated reference for sieve reject, added text about refuse.
16. Added reference to RFC 2822 section 3.6.4 - explains how to
construct references fields.
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 . . . . . . . . . . . . . . . . . . . . . . . . . 7 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 . . . . . . . . . . . 8 4.7 Interaction with Other Sieve Actions . . . . . . . . . . . 9
4.8. Examples . . . . . . . . . . . . . . . . . . . . . . . . . 9 4.8 Examples . . . . . . . . . . . . . . . . . . . . . . . . . 9
5. Response Message Generation . . . . . . . . . . . . . . . . . 9 5. Response Message Generation . . . . . . . . . . . . . . . . . 10
5.1. SMTP MAIL FROM address . . . . . . . . . . . . . . . . . . 9 5.1 SMTP MAIL FROM address . . . . . . . . . . . . . . . . . . 10
5.2. Date . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 5.2 Date . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
5.3. Subject . . . . . . . . . . . . . . . . . . . . . . . . . 10 5.3 Subject . . . . . . . . . . . . . . . . . . . . . . . . . 10
5.4. From . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 5.4 From . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
5.5. To . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 5.5 To . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
5.6. Auto-submitted . . . . . . . . . . . . . . . . . . . . . . 10 5.6 Auto-submitted . . . . . . . . . . . . . . . . . . . . . . 11
5.7. Message Body . . . . . . . . . . . . . . . . . . . . . . . 10 5.7 Message Body . . . . . . . . . . . . . . . . . . . . . . . 11
5.8. In-Reply-To and References . . . . . . . . . . . . . . . . 10 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 . . . . . . . . . . . . . . . . . . . . . . . 10 Electronic Mail . . . . . . . . . . . . . . . . . . . . . . . 11
7. Security Considerations . . . . . . . . . . . . . . . . . . . 10 7. Security Considerations . . . . . . . . . . . . . . . . . . . 11
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12
9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 11 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 12
9.1. Normative References . . . . . . . . . . . . . . . . . . . 11 9.1 Normative References . . . . . . . . . . . . . . . . . . . 12
9.2. Informative References . . . . . . . . . . . . . . . . . . 12 9.2 Informative References . . . . . . . . . . . . . . . . . . 13
Appendix A. Acknowledgements . . . . . . . . . . . . . . . . . . 12 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 13
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 14 A. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 14
Intellectual Property and Copyright Statements . . . . . . . . . . 15 Intellectual Property and Copyright Statements . . . . . . . . 15
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
1.1. 1.1.
The key words "MUST", "MUST NOT", "SHOULD", "SHOULD NOT", "CAN", and The key words "MUST", "MUST NOT", "SHOULD", "SHOULD NOT", "REQUIRED"
"MAY" in this document are to be interpreted as defined in [RFC2119]. and "MAY" in this document are to be interpreted as defined in
[RFC2119].
3. Capability Identifier 3. Capability Identifier
Sieve implementations that implement vacation have an identifier of Sieve implementations that implement vacation have an identifier of
"vacation" for use with the capability mechanism. "vacation" for use with the capability mechanism.
4. Vacation Action 4. Vacation Action
Usage: vacation [":days" number] [":subject" string] Usage: vacation [":days" number] [":subject" string]
[":from" string] [":addresses" string-list] [":from" string] [":addresses" string-list]
skipping to change at page 4, line 41 skipping to change at page 4, line 42
the vacation command available under many versions of Unix. Its the vacation command available under many versions of Unix. Its
purpose is to provide correspondents with notification that the user purpose is to provide correspondents with notification that the user
is away for an extended period of time and that they should not is away for an extended period of time and that they should not
expect quick responses. expect quick responses.
"Vacation" is used to respond to a message with another message. "Vacation" is used to respond to a message with another message.
Vacation's messages are always addressed to the Return-Path address Vacation's messages are always addressed to the Return-Path address
(that is, the envelope from address) of the message being responded (that is, the envelope from address) of the message being responded
to. to.
4.1. Days Parameter 4.1 Days Parameter
The ":days" argument is used to specify the period in which addresses The ":days" argument is used to specify the period in which addresses
are kept and are not responded to, and is always specified in days. are kept and are not responded to, and is always specified in days.
The minimum value used for this parameter is normally 1. Sites MAY The minimum value used for this parameter is normally 1. Sites MAY
define a different minimum value as long as the minimum is greater define a different minimum value as long as the minimum is greater
than 0. Sites MAY also define a maximum days value, which MUST be than 0. Sites MAY also define a maximum days value, which MUST be
greater than 7, and SHOULD be greater than 30. greater than 7, and SHOULD be greater than 30.
If ":days" is omitted, the default value is either 7 or the minimum If ":days" is omitted, the default value is either 7 or the minimum
value (as defined above), whichever is greater. value (as defined above), whichever is greater.
If the parameter given to ":days" is less than the minimum value, If the parameter given to ":days" is less than the minimum value,
then the minimum value is used instead. then the minimum value is used instead.
If ":days" exceeds the site-defined maximum, the site-defined maximum If ":days" exceeds the site-defined maximum, the site-defined maximum
is used instead. is used instead.
4.2. Previous Response Tracking 4.2 Previous Response Tracking
"Vacation" keeps track of all of the responses it has sent to each "Vacation" keeps track of all of the responses it has sent to each
address in some period (as specified by the :days optional argument). address in some period (as specified by the :days optional argument).
If vacation has not previously sent the response to this address If vacation has not previously sent the response to this address
within the given time period, it sends the "reason" argument to the within the given time period, it sends the "reason" argument to the
SMTP MAIL FROM address of the message that is being responded to. SMTP MAIL FROM address [RFC2821] of the message that is being
(The SMTP MAIL FROM address should be available in the Return-path: responded to. (The SMTP MAIL FROM address should be available in the
header field if Sieve processing occurs after final delivery.) Return-path: header field if Sieve processing occurs after final
delivery.)
Tracking is not just per address, but must also take the vacation Tracking is not just per address, but must also take the vacation
response itself into account. A script writer might, for example, response itself into account. A script writer might, for example,
have a vacation action that will send a general notice only once in have a vacation action that will send a general notice only once in
any two-week period. However, even if a sender has received this any two-week period. However, even if a sender has received this
general notice, it may be important to send a specific notice when a general notice, it may be important to send a specific notice when a
message about something timely or something specific has been message about something timely or something specific has been
detected. detected.
A particular vacation response can be identified in one of two ways. A particular vacation response can be identified in one of two ways.
skipping to change at page 7, line 11 skipping to change at page 7, line 6
handle is provided, a hash of the vacation action parameters handle is provided, a hash of the vacation action parameters
specifying the message content and the recipient address. If a specifying the message content and the recipient address. If a
script is changed, implementations MAY reset the records of who has script is changed, implementations MAY reset the records of who has
been responded to and when they have been responded to. been responded to and when they have been responded to.
Implementations are free to limit the number of remembered responses, Implementations are free to limit the number of remembered responses,
provided the limit is no less than 1000. When limiting the number of provided the limit is no less than 1000. When limiting the number of
tracked responses, implementations SHOULD discard the oldest ones tracked responses, implementations SHOULD discard the oldest ones
first. 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
use in the From field of vacation messages. The string must specify use in the From field of vacation messages. The string must specify
a valid [RFC2822] mailbox-list. Implementations SHOULD check the a valid [RFC2822] mailbox-list. Implementations SHOULD check the
syntax and generate an error when a syntactically invalid ":from" syntax and generate an error when a syntactically invalid ":from"
parameter is specified. Implementations MAY also impose restrictions parameter is specified. Implementations MAY also impose restrictions
on what addresses can specified in a ":from" parameter; it is on what addresses can specified in a ":from" parameter; it is
suggested that values which fail such a security check simply be suggested that values which fail such a security check simply be
ignored rather than causing the vacation action to fail. ignored rather than causing the vacation action to fail.
4.4. MIME Parameter 4.4 MIME Parameter
The ":mime" parameter, if supplied, specifies that the reason string The ":mime" parameter, if supplied, specifies that the reason string
is, in fact, a MIME entity as defined in [RFC2045] section 2.4, is, in fact, a MIME entity as defined in [RFC2045] section 2.4,
including both MIME headers and content. including both MIME headers and content.
If the optional :mime parameter is not supplied, the reason string is If the optional :mime parameter is not supplied, the reason string is
considered to be a UTF-8 string. considered to be a UTF-8 string.
4.5. Address Parameter and Limiting Replies to Personal Messages require "vacation";
vacation :mime text:
Content-Type: multipart/alternative; boundary=foo
--foo
I'm at the beach relaxing. Mmmm, surf...
--foo
Content-Type: text/html; charset=us-ascii
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN"
"http://www.w3.org/TR/REC-html40/strict.dtd">
<HTML><HEAD><TITLE>How to relax</TITLE>
<BASE HREF="http://home.example.com/pictures/"></HEAD>
<BODY><P>I'm at the <A HREF="beach.gif">beach</A> relaxing.
Mmmm, <A HREF="ocean.gif">surf</A>...
</BODY></HTML>
--foo--
.
4.5 Address Parameter and Limiting Replies to Personal Messages
"Vacation" MUST NOT respond to a message unless the recipient user's "Vacation" MUST NOT respond to a message unless the recipient user's
email address is in a "To", "Cc", "Bcc", "Resent-To", "Resent-Cc", or email address is in a "To", "Cc", "Bcc", "Resent-To", "Resent-Cc", or
"Resent-Bcc" line of the original message. An email address is "Resent-Bcc" line of the original message. An email address is
considered to belong to the recipient if it is one of: considered to belong to the recipient if it is one of:
1. An email address known by the implementation to be associated 1. An email address known by the implementation to be associated
with the recipient, with the recipient,
2. the final envelope recipient address if it's available to the 2. the final envelope recipient address if it's available to the
skipping to change at page 8, line 4 skipping to change at page 8, line 39
"Vacation" MUST NOT respond to a message unless the recipient user's "Vacation" MUST NOT respond to a message unless the recipient user's
email address is in a "To", "Cc", "Bcc", "Resent-To", "Resent-Cc", or email address is in a "To", "Cc", "Bcc", "Resent-To", "Resent-Cc", or
"Resent-Bcc" line of the original message. An email address is "Resent-Bcc" line of the original message. An email address is
considered to belong to the recipient if it is one of: considered to belong to the recipient if it is one of:
1. An email address known by the implementation to be associated 1. An email address known by the implementation to be associated
with the recipient, with the recipient,
2. the final envelope recipient address if it's available to the 2. the final envelope recipient address if it's available to the
implementation, or implementation, or
3. an address specified by the script writer via the ":addresses" 3. an address specified by the script writer via the ":addresses"
argument described in the next paragraph. argument described in the next paragraph.
Users can supply additional mail addresses that are theirs with the Users can supply additional mail addresses that are theirs with the
":addresses" argument, which takes a string-list listing additional ":addresses" argument, which takes a string-list listing additional
addresses that a user might have. These addresses are considered to addresses that a user might have. These addresses are considered to
belong to the recipient user in addition to the addresses known to belong to the recipient user in addition to the addresses known to
the implementation. the implementation.
4.6. Restricting Replies to Automated Processes and Mailing Lists 4.6 Restricting Replies to Automated Processes and Mailing Lists
Implementations MUST have a list of addresses that "vacation" MUST Implementations MUST have a list of addresses that "vacation" MUST
NOT send mail to. However, the contents of this list are NOT send mail to. However, the contents of this list are
implementation defined. The purpose of this list is to stop mail implementation defined. The purpose of this list is to stop mail
from going to addresses used by system daemons that would not care if from going to addresses used by system daemons that would not care if
the user is actually reading her mail. the user is actually reading her mail.
Implementations are encouraged, however, to include well-known Implementations are encouraged, however, to include well-known
addresses like "MAILER-DAEMON", "LISTSERV", "majordomo", and other addresses like "MAILER-DAEMON", "LISTSERV", "majordomo", and other
addresses typically used only by automated systems. Additionally, addresses typically used only by automated systems. Additionally,
skipping to change at page 8, line 40 skipping to change at page 9, line 28
Implementations SHOULD NOT respond to any message that contains a Implementations SHOULD NOT respond to any message that contains a
"List-Id" [RFC2919], "List-Help", "List-Subscribe", "List- "List-Id" [RFC2919], "List-Help", "List-Subscribe", "List-
Unsubscribe", "List-Post", "List-Owner" or "List-Archive" [RFC2369] Unsubscribe", "List-Post", "List-Owner" or "List-Archive" [RFC2369]
header field. header field.
Implementations SHOULD NOT respond to any message that has an "Auto- Implementations SHOULD NOT respond to any message that has an "Auto-
submitted" header field with a value other than "no". This header submitted" header field with a value other than "no". This header
field is described in [RFC3834]. field is described in [RFC3834].
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 will fail if Vacation can only be executed once per script. A script will fail if
it attempts to execute two or more vacation actions. it attempts to execute two or more 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 [I-D.ietf-sieve-refuse-
reject]. 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.
If it's an emergency, call 911, I guess." ; If it's an emergency, call 911, I guess." ;
By mingling vacation with other rules, users can do something more By mingling vacation with other rules, users can do something more
skipping to change at page 9, line 40 skipping to change at page 10, line 27
It is worth noting that the input message and arguments may be in It is worth noting that the input message and arguments may be in
UTF-8, and that implementations MUST deal with UTF-8 input, although UTF-8, and that implementations MUST deal with UTF-8 input, although
implementations MAY transcode to other character sets as regional implementations MAY transcode to other character sets as regional
taste dictates. When :mime is used the reason argument also contains taste dictates. When :mime is used the reason argument also contains
MIME header information. The headers must conform to MIME MIME header information. The headers must conform to MIME
conventions; in particular, 8bit text is not allowed. conventions; in particular, 8bit text is not allowed.
Implementations SHOULD reject vacation :mime actions containing 8bit Implementations SHOULD reject vacation :mime actions containing 8bit
header material. header material.
5.1. SMTP MAIL FROM address 5.1 SMTP MAIL FROM address
The SMTP MAIL FROM address of the message envelope SHOULD be set to The SMTP MAIL FROM address of the message envelope SHOULD be set to
<>. NOTIFY=NEVER SHOULD also be set in the RCPT TO line during the <>. NOTIFY=NEVER SHOULD also be set in the RCPT TO line during the
SMTP transaction if the NOTARY SMTP extension [RFC3461]is available. SMTP transaction if the NOTARY SMTP extension [RFC3461]is available.
5.2. Date 5.2 Date
The Date field SHOULD be set to the date and time when the vacation The Date field SHOULD be set to the date and time when the vacation
response was generated. Note that this may not be the same as the response was generated. Note that this may not be the same as the
time the message was delivered to the user. time the message was delivered to the user.
5.3. Subject 5.3 Subject
Users can specify the Subject of the reply with the ":subject" Users can specify the Subject of the reply with the ":subject"
parameter. If the :subject parameter is not supplied, then the parameter. If the :subject parameter is not supplied, then the
subject is generated as follows: The subject is set to the characters subject is generated as follows: The subject is set to the characters
"Auto: " followed by the original subject. "Auto: " followed by the original subject.
5.4. From 5.4 From
Unless explicitly overridden with a :from parameter, the From field Unless explicitly overridden with a :from parameter, the From field
SHOULD be set to the address of the owner of the Sieve script. SHOULD be set to the address of the owner of the Sieve script.
5.5. To 5.5 To
The To field SHOULD be set to the address of the recipient of the The To field SHOULD be set to the address of the recipient of the
response. response.
5.6. Auto-submitted 5.6 Auto-submitted
An Auto-Submitted field with a value of "auto-replied" SHOULD be An Auto-Submitted field with a value of "auto-replied" SHOULD be
included in the message header of any vacation message sent. included in the message header of any vacation message sent.
5.7. Message Body 5.7 Message Body
The body of the message is taken from the reason string in the The body of the message is taken from the reason string in the
vacation command. vacation command.
5.8. In-Reply-To and References 5.8 In-Reply-To and References
Replies MUST have the In-Reply-To field set to the Message-ID of the Replies MUST have the In-Reply-To field set to the Message-ID of the
original message, and the References field SHOULD be updated with the original message, and the References field SHOULD be updated with the
Message-ID of the original message. Message-ID of the original message.
If the original message lacks a Message-ID, an In-Reply-To need not If the original message lacks a Message-ID, an In-Reply-To need not
be generated, and References need not be changed. be generated, and References need not be changed.
Section 3.6.2 of [RFC2822] provides a complete description of how
References fields should be generated.
6. Relationship to Recommendations for Automatic Responses to 6. Relationship to Recommendations for Automatic Responses to
Electronic Mail Electronic Mail
The vacation extension implements a "Personal Responder" in the The vacation extension implements a "Personal Responder" in the
terminology defined in [RFC3834]. Care has been taken in this terminology defined in [RFC3834]. Care has been taken in this
specification to comply with the recommendations [RFC3834] makes in specification to comply with the recommendations [RFC3834] makes in
regards to how personal responders should behave. regards to how personal responders should behave.
7. Security Considerations 7. Security Considerations
It is critical that implementations correctly implement the behavior It is critical that implementations correctly implement the behavior
and restrictions described throughout this document. Replies MUST and restrictions described throughout this document. Replies MUST
NOT be sent out in response to messages not sent directly to the NOT be sent out in response to messages not sent directly to the
user, and replies MUST NOT be sent out more often than the :days user, and replies MUST NOT be sent out more often than the :days
argument states unless the script changes. argument states unless the script changes.
If mail is forwarded from a site that uses subaddressing, it may be If mail is forwarded from a site that uses subaddressing, it may be
impossible to list all recipient addresses with ":addresses". impossible to list all recipient addresses with ":addresses".
Security issues associated with mail auto-responders are fully Security issues associated with mail auto-responders are fully
skipping to change at page 11, line 39 skipping to change at page 12, line 28
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:
Ned Freed Ned Freed
E-Mail: 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.
9. References 9. References
9.1. Normative References 9.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-04 (work in progress),
July 2005, <http://www.ietf.org/internet-drafts/ July 2005, <http://www.ietf.org/internet-drafts/
draft-ietf-sieve-3028bis-04.txt>. draft-ietf-sieve-3028bis-04.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-04 (work in
skipping to change at page 12, line 29 skipping to change at page 13, line 16
[RFC2822] Resnick, P., "Internet Message Format", RFC 2822, [RFC2822] Resnick, P., "Internet Message Format", RFC 2822,
April 2001. April 2001.
[RFC3461] Moore, K., "Simple Mail Transfer Protocol (SMTP) Service [RFC3461] Moore, K., "Simple Mail Transfer Protocol (SMTP) Service
Extension for Delivery Status Notifications (DSNs)", Extension for Delivery Status Notifications (DSNs)",
RFC 3461, January 2003. RFC 3461, January 2003.
[RFC3834] Moore, K., "Recommendations for Automatic Responses to [RFC3834] Moore, K., "Recommendations for Automatic Responses to
Electronic Mail", RFC 3834, August 2004. Electronic Mail", RFC 3834, August 2004.
9.2. Informative References 9.2 Informative References
[I-D.ietf-sieve-refuse-reject] [I-D.ietf-sieve-refuse-reject]
Elvey, M. and A. Melnikov, "The SIEVE mail filtering Elvey, M. and A. Melnikov, "The SIEVE mail filtering
language - reject and refuse extensions", language - reject and refuse extensions",
draft-ietf-sieve-refuse-reject (work in progress), draft-ietf-sieve-refuse-reject (work in progress),
May 2005, <http://www.ietf.org/internet-drafts/ May 2005, <http://www.ietf.org/internet-drafts/
draft-ietf-sieve-refuse-reject.txt>. draft-ietf-sieve-refuse-reject.txt>.
[RFC2142] Crocker, D., "MAILBOX NAMES FOR COMMON SERVICES, ROLES AND [RFC2142] Crocker, D., "MAILBOX NAMES FOR COMMON SERVICES, ROLES AND
FUNCTIONS", RFC 2142, May 1997. FUNCTIONS", RFC 2142, May 1997.
[RFC2369] Neufeld, G. and J. Baer, "The Use of URLs as Meta-Syntax [RFC2369] Neufeld, G. and J. Baer, "The Use of URLs as Meta-Syntax
for Core Mail List Commands and their Transport through for Core Mail List Commands and their Transport through
Message Header Fields", RFC 2369, July 1998. Message Header Fields", RFC 2369, July 1998.
[RFC2821] Klensin, J., "Simple Mail Transfer Protocol", RFC 2821,
April 2001.
[RFC2919] Chandhok, R. and G. Wenger, "List-Id: A Structured Field [RFC2919] Chandhok, R. and G. Wenger, "List-Id: A Structured Field
and Namespace for the Identification of Mailing Lists", and Namespace for the Identification of Mailing Lists",
RFC 2919, March 2001. RFC 2919, March 2001.
Appendix A. Acknowledgements
This extension is obviously inspired by Eric Allman's vacation
program under Unix. The authors owe a great deal to Carnegie Mellon
University, Cyrus Daboo, Lawrence Greenfield, Michael Haardt, Kjetil
Torgrim Homme, Arnt Gulbrandsen, Mark Mallet, Alexey Melnikov,
Jeffrey Hutzelman and many others whose names have been lost during
the inexcusably long gestation period of this document.
Authors' Addresses Authors' Addresses
Tim Showalter Tim Showalter
?? ??
Email: tjs@psaux.com Email: tjs@psaux.com
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
Appendix A. Acknowledgements
This extension is obviously inspired by Eric Allman's vacation
program under Unix. The authors owe a great deal to Carnegie Mellon
University, Cyrus Daboo, Lawrence Greenfield, Michael Haardt, Kjetil
Torgrim Homme, Arnt Gulbrandsen, Mark Mallet, Alexey Melnikov,
Jeffrey Hutzelman, Philip Guenther and many others whose names have
been lost during the inexcusably long gestation period of this
document.
Intellectual Property Statement Intellectual Property Statement
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.
 End of changes. 34 change blocks. 
63 lines changed or deleted 99 lines changed or added

This html diff was produced by rfcdiff 1.27, available from http://www.levkowetz.com/ietf/tools/rfcdiff/