idnits 2.17.1 draft-showalter-sieve-vacation-03.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** Missing expiration date. The document expiration date should appear on the first and last page. == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The document seems to lack a both a reference to RFC 2119 and the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords. RFC 2119 keyword, line 96: '...is parameter is 1. Sites MAY define a...' RFC 2119 keyword, line 97: '...um value. Sites MAY also define a max...' RFC 2119 keyword, line 98: '... which MUST be greater than 7, and S...' RFC 2119 keyword, line 133: '...triggered. This behavior is REQUIRED....' RFC 2119 keyword, line 135: '... implementations MAY reset the records...' (7 more instances...) Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == Line 80 has weird spacing: '...command avail...' == Line 208 has weird spacing: '...acation is u...' == Line 211 has weird spacing: '...ed with disca...' == Line 224 has weird spacing: '...ers can do s...' == Line 256 has weird spacing: '...., "Key words...' == (12 more instances...) -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (May 8, 2000) is 8751 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) -- Missing reference section? 'SIEVE' on line 266 looks like a reference -- Missing reference section? 'KEYWORDS' on line 256 looks like a reference -- Missing reference section? 'MAILBOXNAMES' on line 259 looks like a reference -- Missing reference section? 'MIME' on line 262 looks like a reference Summary: 4 errors (**), 0 flaws (~~), 8 warnings (==), 6 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Network Working Group T. Showalter 2 Internet Draft: Sieve: Vacation Extension Mirapoint 3 Document: draft-showalter-sieve-vacation-03.txt May 8, 2000 4 Expire in six months 6 Sieve: Vacation Extension 8 Status of this memo 10 This document is an Internet-Draft and is in full conformance with 11 all provisions of Section 10 of RFC2026. 13 Internet-Drafts are working documents of the Internet Engineering 14 Task Force (IETF), its areas, and its working groups. Note that 15 other groups may also distribute working documents as Internet- 16 Drafts. 18 Internet-Drafts are draft documents valid for a maximum of six months 19 and may be updated, replaced, or obsoleted by other documents at any 20 time. It is inappropriate to use Internet-Drafts as reference 21 material or to cite them other than as "work in progress." 23 The list of current Internet-Drafts can be accessed at 24 http://www.ietf.org/ietf/1id-abstracts.txt 26 The list of Internet-Draft Shadow Directories can be accessed at 27 http://www.ietf.org/shadow.html 29 Copyright 31 Copyright (C) The Internet Society 2000. All Rights Reserved. 33 Abstract 35 This document describes an extension to the Sieve mail filtering 36 language for an autoresponder similar to that of the Unix "vacation" 37 command for replying to messages with certain safety features to 38 prevent problems. 40 Internet DRAFT Sieve: Vacation Extension May 8, 2000 42 0. Meta-information on this draft 44 This information is intended to facilitate discussion. It will be 45 removed when this document leaves the Internet-Draft stage. 47 0.1. Discussion 49 This draft is intended to be an extension to the Sieve mail filtering 50 language, avaliable from the Internet-Drafts repository as 51 52 (where 10 is the version number, which is currently 10). 54 This draft and the Sieve language itself are being discussed on the 55 MTA Filters mailing list at . Subscription 56 requests can be sent to (send an 57 email message with the word "subscribe" in the body). More 58 information on the mailing list along with a WWW archive of back 59 messages is available at . 61 1. Introduction 63 This is an extension to the Sieve language defined by [SIEVE] for 64 notification that messages will not be immediately answered. 66 Conventions for notations are as in [SIEVE] section 1.1, including 67 use of [KEYWORDS]. 69 2. Capability Identifier 71 Sieve implementations that implement vacation have an identifier of 72 "vacation" for use with the capability mechanism. 74 3. Vacation Action 76 Syntax: vacation [":days" number] [":addresses" string-list] 77 [":subject" string] [":mime"] 79 The "vacation" action implements a vacation autoresponder similar to 80 the vacation command available under many versions of Unix. Its 81 purpose is to provide correspondents with notification that the user 82 is away for an extended period of time and that they should not 83 expect quick responses. 85 "Vacation" is used to respond to a message with another message. 86 Vacation's messages are always addressed to the Return-Path address 87 (that is, the envelope from address) of the message being responded 88 to. 90 Internet DRAFT Sieve: Vacation Extension May 8, 2000 92 3.1. Days Parameter 94 The ":days" argument is used to specify the period in which addresses 95 are kept and are not responded to, and is always specified in days. 96 The minimum value used for this parameter is 1. Sites MAY define a 97 different minimum value. Sites MAY also define a maximum days value, 98 which MUST be greater than 7, and SHOULD be greater than 30. 100 If ":days" is omitted, the default value is either 7 or the minimum 101 value (as defined above), whichever is greater. 103 If the parameter given to ":days" is less than the minimum value, 104 then the minimum value is used instead. 106 If ":days" exceeds the site-defined maximum, the site-defined maximum 107 is used instead. 109 3.2. Previous Response Tracking 111 "Vacation" keeps track of all of the addresses that it has responded 112 to in some period (as specified by the :days optional argument). If 113 vacation has not previously responded to this address within that 114 time period, it sends the "reason" argument to the Return-Path 115 address of the message that is being responded to. 117 Vacation responses are not just per address, but are per address per 118 vacation command. For instance, If coyote@desert sends mail to 119 roadrunner@acme, once with the subject "Cyrus bug" and once with the 120 subject "come over for dinner", and roadrunner@acme has the script 121 below, coyote@desert would receive two responses, once with the first 122 message, once with the second. 124 Example: require "vacation"; 125 if subject :contains "cyrus" { 126 vacation "I'm out -- send mail to cyrus-bugs"; 127 } else { 128 vacation "I'm out -- call me at 304 555 1212"; 129 } 131 Note that coyote@desert gets the second message despite having gotten 132 the first one because separate vacation responses have been 133 triggered. This behavior is REQUIRED. 135 If a sieve script changes, implementations MAY reset the records of 136 who has been responded to and when they have been responded to. 137 Alternatively, implementations can store records of who has received 138 which message, perhaps by storing a hash of the message and the 140 Internet DRAFT Sieve: Vacation Extension May 8, 2000 142 recipient. 144 3.3. Subject Parameter 146 Users can specify the subject of the reply with the ":subject" 147 parameter. If the :subject parameter is not supplied, then the 148 subject is generated as follows: The subject is set to the characters 149 "Re: " followed by the original subject with all leading occurrence 150 of the characters "Re: " stripped off. 152 3.4. MIME Parameter 154 The ":mime" parameter, if supplied, specifies that the reason string 155 is, in fact, a MIME part, including MIME headers (see section 2.4.2.4 156 of [SIEVE]). 158 If the optional :mime parameter is not supplied, the reason string is 159 considered to be a UTF-8 string. 161 3.5. In-Reply-To 163 Replies MUST have the In-Reply-To field set to the Message-ID of the 164 original message. 166 3.6. Address Parameter and Limiting Replies to Personal Messages 168 "Vacation" MUST NOT respond to a message unless the user's email 169 address is in the "To", "Cc", or "Bcc" line of the original message. 170 Implementations are assumed to know the user's email address, but 171 users may have additional addresses beyond the control of the local 172 mail system. 174 Users can supply additional mail addresses that are theirs with the 175 ":addresses" argument, which takes a string-list listing additional 176 addresses that a user might have. These addresses are considered in 177 addition to the addresses that the implementation knows. 179 3.7. Restricting Replies to Automated Processes and Mailing Lists 181 Implementations MUST have a list of addresses that "vacation" MUST 182 NOT send mail to. However, the contents of this list are 183 implementation defined. The purpose of this list is to stop mail 184 from going to addresses used by system daemons that would not care if 185 the user is actually reading her mail. 187 Implementations are encouraged, however, to include well-known 188 addresses like "MAILER-DAEMON", "LISTSERV", "majordomo", and other 189 addresses typically used only by automated systems. Additionally, 191 Internet DRAFT Sieve: Vacation Extension May 8, 2000 193 addresses ending in "-request" or beginning in "owner-", i.e., 194 reserved for mailing list software, are also suggested. 196 Implementors may take guidance from [MAILBOXNAMES], but should be 197 careful. Some addresses, like "POSTMASTER", are generally actually 198 managed by people, and people do care if the user is going to be 199 unavailable. 201 Implementations SHOULD NOT not to respond to any message with a 202 header that begins with "List-". 204 3.8. Interaction with Other Sieve Actions 206 Vacation does not affect the implicit keep. 208 Vacation can only be executed once per script. If vacation is used 209 with another vacation, the script fails. 211 Implementations MUST NOT consider vacation used with discard, keep, 212 fileinto, or redirect an error. 214 3.9. Examples 216 Here is a simple use of vacation. 218 Example: require "vacation"; 219 vacation :days 23 220 :addresses ["tjs@znic.edu", "ts4z@landru.edu"] 221 "I'm away until October 19. 222 If it's an emergency, call 911, I guess." ; 224 By mingling vacation with other rules, users can do something more 225 selective. 227 Example: require "vacation"; 228 if header :contains "from" "boss@frobnitzm.edu" { 229 redirect "pleeb@xanadu.wv.us"; 230 } else { 231 vacation "Sorry, I'm away, I'll read your message 232 when I get around to it."; 233 } 235 4. Security Considerations 236 It is critical that implementations correctly implement the 237 limitations described above. Replies MUST NOT be sent out in 238 response to messages not sent directly to the user, and replies MUST 239 NOT be sent out more often than the :days argument states. 241 Internet DRAFT Sieve: Vacation Extension May 8, 2000 243 5. Author's Address 245 Tim Showalter 246 Mirapoint, Inc. 247 Two Results Way, Suite 100 248 Cupertino, CA 95014 250 E-Mail: tjs@mirapoint.com 252 Internet DRAFT Sieve: Vacation Extension May 8, 2000 254 Appendix A. References 256 [KEYWORDS] Bradner, S., "Key words for use in RFCs to Indicate 257 Requirement Levels", RFC 2119, Harvard University, March 1997. 259 [MAILBOXNAMES] Crocker, D. "Mailbox Names for Common Services, Roles, 260 and Functions", RFC 2142, Internet Mail Consortium, May, 1997. 262 [MIME] Freed, N., and N. Borenstein, "Multipurpose Internet Mail 263 Extensions (MIME) Part One: Format of Internet Message Bodies", RFC 264 2045, Innosoft and First Virtual, November 1996. 266 [SIEVE] Showalter, T., "Sieve: A Mail Filtering Language", 267 Mirapoint, Inc., Work in Progress. 269 Appendix B. Full Copyright Statement 271 Copyright (C) The Internet Society 2000. All Rights Reserved. 273 This document and translations of it may be copied and furnished to 274 others, and derivative works that comment on or otherwise explain it 275 or assist in its implementation may be prepared, copied, published 276 and distributed, in whole or in part, without restriction of any 277 kind, provided that the above copyright notice and this paragraph are 278 included on all such copies and derivative works. However, this 279 document itself may not be modified in any way, such as by removing 280 the copyright notice or references to the Internet Society or other 281 Internet organizations, except as needed for the purpose of 282 developing Internet standards in which case the procedures for 283 copyrights defined in the Internet Standards process must be 284 followed, or as required to translate it into languages other than 285 English. 287 The limited permissions granted above are perpetual and will not be 288 revoked by the Internet Society or its successors or assigns. 290 This document and the information contained herein is provided on an 291 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 292 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 293 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 294 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 295 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.