idnits 2.17.1 draft-showalter-sieve-vacation-01.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.) ** There is 1 instance of too long lines in the document, the longest one being 5 characters in excess of 72. ** 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 100: '...is parameter is 1. Sites MAY define a...' RFC 2119 keyword, line 101: '...um value. Sites MAY also define a max...' RFC 2119 keyword, line 102: '... which MUST be greater than 7, and S...' RFC 2119 keyword, line 167: '...d above: Replies MUST NOT be sent out ...' RFC 2119 keyword, line 168: '...y to the user, and replies MUST NOT be...' Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == Line 86 has weird spacing: '...command avail...' == Line 184 has weird spacing: '...., "Key words...' == Line 194 has weird spacing: '...ied and furni...' == Line 196 has weird spacing: '... may be prepa...' == Line 197 has weird spacing: '... and distri...' == (9 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 (February 24, 1999) is 9193 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 187 looks like a reference -- Missing reference section? 'KEYWORDS' on line 184 looks like a reference Summary: 5 errors (**), 0 flaws (~~), 8 warnings (==), 4 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group T. Showalter 3 Internet Draft: Sieve: Vacation Extension Carnegie Mellon 4 Document: draft-showalter-sieve-vacation-01.txt February 24, 1999 5 Expire in six months 7 Sieve: Vacation Extension 9 Status of this memo 11 This document is an Internet-Draft and is in full conformance with 12 all provisions of Section 10 of RFC2026. 14 Internet-Drafts are working documents of the Internet Engineering 15 Task Force (IETF), its areas, and its working groups. Note that 16 other groups may also distribute working documents as Internet- 17 Drafts. 19 Internet-Drafts are draft documents valid for a maximum of six months 20 and may be updated, replaced, or obsoleted by other documents at any 21 time. It is inappropriate to use Internet-Drafts as reference 22 material or to cite them other than as "work in progress." 24 The list of current Internet-Drafts can be accessed at 25 http://www.ietf.org/ietf/1id-abstracts.txt 27 The list of Internet-Draft Shadow Directories can be accessed at 28 http://www.ietf.org/shadow.html 30 The protocol discussed in this document is experimental and subject 31 to change. Persons planning on either implementing or using this 32 protocol are STRONGLY URGED to get in touch with the author before 33 embarking on such a project. 35 Copyright 37 Copyright (C) The Internet Society 1999. All Rights Reserved. 39 Abstract 41 This document describes an extension to the Sieve mail filtering 42 language for an autoresponder similar to that of the Unix "vacation" 43 command for replying to messages with certain safety features to 44 prevent problems. 46 Internet DRAFT Sieve: Vacation Extension February 24, 1999 48 0. Meta-information on this draft 50 This information is intended to facilitate discussion. It will be 51 removed when this document leaves the Internet-Draft stage. 53 0.1. Discussion 55 This draft is intended to be an extension to the Sieve mail filtering 56 language, avaliable from the Internet-Drafts repository as 57 58 (where 07 is the version number, which is actually currently 07). 60 This draft and the Sieve language itself are being discussed on the 61 MTA Filters mailing list at . Subscription 62 requests can be sent to (send an 63 email message with the word "subscribe" in the body). More 64 information on the mailing list along with a WWW archive of back 65 messages is available at . 67 1. Introduction 69 This is an extension to the Sieve language defined by [SIEVE] for 70 notification that messages will not be immediately answered. 72 Conventions for notations are as in [SIEVE] section 1.1, including 73 use of [KEYWORDS]. 75 2. Capability Identifier 77 Sieve implementations that implement vacation have an identifier of 78 "vacation" for use with the capability mechanism. 80 3. Vacation Action 82 Syntax: vacation [":days" number] [":addresses" string-list] 83 [":subject" string] 85 The "vacation" action implements a vacation autoresponder similar to 86 the vacation command available under many versions of Unix. Its 87 purpose is to provide correspondents with notification that the user 88 is away for an extended period of time and that they should not 89 expect quick responses. 91 "Vacation" is used to respond to a message with another message. 92 Vacation's messages are always addressed to the Return-Path address 93 (that is, the envelope from address) of the message being responded 94 to. 96 Internet DRAFT Sieve: Vacation Extension February 24, 1999 98 The ":days" argument is used to specify the period in which addresses 99 are kept and are not responded to, and is always specified in days. 100 The minimum value used for this parameter is 1. Sites MAY define a 101 different minimum value. Sites MAY also define a maximum days value, 102 which MUST be greater than 7, and SHOULD be greater than 30. 104 If ":days" is omitted, the default value is 7, or the minimum value 105 (as defined above), whichever is greater. 107 If the parameter given to ":days" is greater than the minimum value, 108 then the minimum value is used instead. 110 If ":days" exceeds the site-defined maximum, the site-defined maximum 111 is used instead. 113 "Vacation" keeps track of all of the addresses that it has responded 114 to in some period (as specified by the :days optional argument). If 115 vacation has not previously responded to this address within that 116 time period, it sends the "reason" argument to the Return-Path 117 address of the message that is being responded to. 119 "Vacation" never responds to a message unless the user's email 120 address is in the "To" or "Cc" line of the original message. 121 Implementations are assumed to be able to know this information, but 122 users may have additional addresses beyond the control of the local 123 mail system. 125 Users can supply additional mail addresses that are theirs with the 126 ":addresses" argument, which takes a string-list listing additional 127 addresses that a user might have. 129 Users can specify the subject of the reply with the ":subject" 130 parameter. If the :subject parameter is not supplied, then the 131 subject is generated as follows: The subject is set to the characters 132 "Re: " followed by the original subject with all leading occurrence 133 of the characters "Re: " stripped off. 135 Replies must have the In-Reply-To field set to the Message-ID of the 136 original message. 138 Example: 139 require "vacation"; 140 vacation :days 23 :addresses ["tjs@znic.edu", "ts4z@landru.edu"] 141 "I'm away until October 19. If it's an emergency, call 142 911, I guess." ; 144 By mingling vacation with other rules, users can do something more 145 selective. 147 Internet DRAFT Sieve: Vacation Extension February 24, 1999 149 Example: 150 require "vacation"; 151 if header :contains "from" "boss@frobnitzm.edu" { 152 redirect "pleeb@xanadu.wv.us"; 153 } else { 154 vacation "Sorry, I'm away, I'll read your message 155 when I get around to it."; 156 } 158 4. Interaction with Other Sieve Actions 160 Vacation does not affect the implicit keep. 162 Vacation may not be used with reject. 164 5. Security Considerations 166 It is critical that implementations correctly implement the 167 limitations described above: Replies MUST NOT be sent out in response 168 to messages not sent directly to the user, and replies MUST NOT be 169 sent out more often than the :days argument states. 171 6. Author's Address 173 Tim Showalter 174 Carnegie Mellon University 175 5000 Forbes Avenue 176 Pittsburgh, PA 15213 178 E-Mail: tjs+@andrew.cmu.edu 180 Internet DRAFT Sieve: Vacation Extension February 24, 1999 182 Appendix A. References 184 [KEYWORDS] Bradner, S., "Key words for use in RFCs to Indicate 185 Requirement Levels", RFC 2119, Harvard University, March 1997. 187 [SIEVE] Showalter, T., "Sieve: A Mail Filtering Language", Carnegie 188 Mellon, Work in Progress. 190 Appendix B. Full Copyright Statement 192 Copyright (C) The Internet Society 1999. All Rights Reserved. 194 This document and translations of it may be copied and furnished to 195 others, and derivative works that comment on or otherwise explain it 196 or assist in its implementation may be prepared, copied, published 197 and distributed, in whole or in part, without restriction of any 198 kind, provided that the above copyright notice and this paragraph are 199 included on all such copies and derivative works. However, this 200 document itself may not be modified in any way, such as by removing 201 the copyright notice or references to the Internet Society or other 202 Internet organizations, except as needed for the purpose of 203 developing Internet standards in which case the procedures for 204 copyrights defined in the Internet Standards process must be 205 followed, or as required to translate it into languages other than 206 English. 208 The limited permissions granted above are perpetual and will not be 209 revoked by the Internet Society or its successors or assigns. 211 This document and the information contained herein is provided on an 212 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 213 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 214 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 215 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 216 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 218 This document will expire before 31 July 1999.