idnits 2.17.1 draft-freed-sieve-notary-09.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** You're using the IETF Trust Provisions' Section 6.b License Notice from 12 Sep 2009 rather than the newer Notice from 28 Dec 2009. (See https://trustee.ietf.org/license-info/) Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- 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 26, 2010) is 5056 days in the past. Is this intentional? -- Found something which looks like a code comment -- if you have code sections in the document, please surround them with '' and '' lines. 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: 'COMPARATOR' is mentioned on line 286, but not defined == Missing Reference: 'ADDRESS-PART' is mentioned on line 286, but not defined == Missing Reference: 'MATCH-TYPE' is mentioned on line 287, but not defined -- Obsolete informational reference (is this intentional?): RFC 3501 (Obsoleted by RFC 9051) Summary: 1 error (**), 0 flaws (~~), 4 warnings (==), 4 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Sieve Working Group N. Freed 3 Internet-Draft Oracle 4 Intended status: Standards Track May 26, 2010 5 Expires: November 27, 2010 7 Sieve Email Filtering: Delivery Status Notifications and Deliver-By 8 Extensions 9 draft-freed-sieve-notary-09 11 Abstract 13 This document describes the "envelope-dsn", "redirect-dsn", 14 "envelope-deliverby", and "redirect-deliverby" extensions to the 15 Sieve email filtering language. The "envelope-dsn" and "envelope- 16 deliverby" extensions provide access to additional envelope 17 information provided by the delivery status notification and 18 deliver-by SMTP extensions, respectively. The "redirect-dsn" and 19 "redirect-deliverby" extensions extend Sieve's redirect action to 20 provide control over delivery status notification and deliver-by 21 parameters, respectively. 23 Change History (to be removed prior to publication as an RFC 25 Correct RFC 2852 section reference. 27 Removed some extraneous [ characters from a couple of figures. 29 Clarified orcpt decoding. 31 Changed the ABNF for notary values to disallow spaces. 33 Fixed several typos. 35 Changed name of extension from notary to envelope-dsn. 37 Added the redirect-dsn extension. 39 Updated references. 41 Added a note about the use of ADDRESS-PART arguments with the new 42 envelope-part strings defined by the envelope-dsn extension. 44 Fleshed out the redirect-dsn extension. 46 Changed document title to agree with new extension names. 48 Added some examples. 50 Fixed more typos. 52 Changed dsn-envelope and dsn-redirect to envelope-dsn and redirect- 53 dsn, respectively. 55 Added a redirect-dsn example. 57 Added the two deliver-by extensions. 59 Added requirements text regarding envelope sender address selection. 61 Added various clarifications about negative by-time values. 63 Added a pointer to the conventions section to where Sieve errors are 64 discussed. 66 Clearified test failure text in both envelope extensions. 68 Addeed the ability to deal with by-times as either absolute ISO 8601 69 or relative integer values. 71 Status of this Memo 73 This Internet-Draft is submitted to IETF in full conformance with the 74 provisions of BCP 78 and BCP 79. 76 Internet-Drafts are working documents of the Internet Engineering 77 Task Force (IETF), its areas, and its working groups. Note that 78 other groups may also distribute working documents as Internet- 79 Drafts. 81 Internet-Drafts are draft documents valid for a maximum of six months 82 and may be updated, replaced, or obsoleted by other documents at any 83 time. It is inappropriate to use Internet-Drafts as reference 84 material or to cite them other than as "work in progress." 86 The list of current Internet-Drafts can be accessed at 87 http://www.ietf.org/ietf/1id-abstracts.txt. 89 The list of Internet-Draft Shadow Directories can be accessed at 90 http://www.ietf.org/shadow.html. 92 This Internet-Draft will expire on November 27, 2010. 94 Copyright Notice 96 Copyright (c) 2010 IETF Trust and the persons identified as the 97 document authors. All rights reserved. 99 This document is subject to BCP 78 and the IETF Trust's Legal 100 Provisions Relating to IETF Documents 101 (http://trustee.ietf.org/license-info) in effect on the date of 102 publication of this document. Please review these documents 103 carefully, as they describe your rights and restrictions with respect 104 to this document. Code Components extracted from this document must 105 include Simplified BSD License text as described in Section 4.e of 106 the Trust Legal Provisions and are provided without warranty as 107 described in the BSD License. 109 Table of Contents 111 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4 112 2. Conventions used in this document . . . . . . . . . . . . . . 4 113 3. Capability Identifiers . . . . . . . . . . . . . . . . . . . . 5 114 4. Envelope-dsn Extension . . . . . . . . . . . . . . . . . . . . 5 115 4.1. Examples . . . . . . . . . . . . . . . . . . . . . . . . . 6 116 5. Envelope-deliverby Extension . . . . . . . . . . . . . . . . . 7 117 5.1. Examples . . . . . . . . . . . . . . . . . . . . . . . . . 8 118 6. redirect-dsn extension . . . . . . . . . . . . . . . . . . . . 10 119 6.1. MAIL FROM address selection . . . . . . . . . . . . . . . 10 120 6.2. Example . . . . . . . . . . . . . . . . . . . . . . . . . 10 121 7. redirect-deliverby extension . . . . . . . . . . . . . . . . . 11 122 7.1. MAIL FROM address selection . . . . . . . . . . . . . . . 12 123 7.2. Example . . . . . . . . . . . . . . . . . . . . . . . . . 12 124 8. Security Considerations . . . . . . . . . . . . . . . . . . . 12 125 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14 126 10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 15 127 10.1. Normative references . . . . . . . . . . . . . . . . . . . 15 128 10.2. Informative references . . . . . . . . . . . . . . . . . . 15 129 Appendix A. Acknowledgements . . . . . . . . . . . . . . . . . . 15 130 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 16 132 1. Introduction 134 Sieve [RFC5228] is a language for filtering email messages at or 135 around the time of final delivery. It is designed to be 136 implementable on either a mail client or mail server. It is suitable 137 for running on a mail server where users may not be allowed to 138 execute arbitrary programs, such as on black box Internet Message 139 Access Protocol [RFC3501] servers, as it has no user-controlled loops 140 or the ability to run external programs. 142 The base sieve specification defines the envelope extension and test 143 to access information in the message envelope. Only information 144 available in regular SMTP [RFC5321] is provided; additional 145 information added to the SMTP envelope by SMTP extensions cannot be 146 accessed. 148 The "envelope-dsn" extension extends the envelope test to allow 149 access to the additional envelope fields defined by the SMTP 150 extension for delivery status notification specified in RFC 3461 151 [RFC3461]. The "envelope-deliverby" extension extends the envelope 152 test to allow access to the additional envelope fields defined by the 153 deliver-by SMTP extension defined in [RFC2852]. 155 The base sieve specification also defines the redirect action, which 156 sends the message to a different address. Redirect only allows 157 specification of the new recipient address. The "redirect-dsn" 158 extension extends redirect to allow specification of some fields 159 defined by the delivery status notification SMTP extension. 160 "redirect-deliverby" in turn provides the ability to set a time limit 161 for delivery as specified in RFC 2852 [RFC2852]. 163 2. Conventions used in this document 165 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 166 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 167 document are to be interpreted as described in [RFC2119]. 169 The terms used to describe the various components of the Sieve 170 language are taken from Section 1.1 of [RFC5228]. The nature and 171 handling of Sieve errors is described in Section 2.10.6. 173 This document uses the ABNF notation specified in [RFC5234], and 174 refers to the ABNF productions notify-esmtp-value defined in Section 175 4.1 of [RFC3461]. 177 3. Capability Identifiers 179 The capability strings associated with the extensions defined in this 180 document are "envelope-dsn", "redirect-dsn", "envelope-deliverby", 181 and "redirect-deliverby". 183 4. Envelope-dsn Extension 185 The "envelope-dsn" extension does not define any new tests or 186 actions, rather, it adds four values to the list of possible (case- 187 insensitive) envelope-part strings defined in Section 5.4 of 188 [RFC5228]: 190 notify - Match the list of notification conditions, or NOTIFY 191 values, associated with the TO address used in the SMTP RCPT TO 192 command that resulted in this message getting delivered to this 193 user. More than one notification condition can be in effect at 194 once; each condition that is in effect is tested separately and 195 any match causes the test to succeed. The syntax and semantics of 196 the NOTIFY parameter are defined in Section 4.1 of RFC 3461 197 [RFC3461] . Currently the possible notification condition values 198 are "NEVER", "SUCCESS", "FAILURE" and "DELAY". Note that the 199 value "NEVER" is never combined with any other value. 201 orcpt - Match the original recipient, or ORCPT, value associated 202 with the TO address used in the SMTP RCPT TO command that resulted 203 in this message getting delivered to this user, with xtext 204 encoding removed. The syntax and semantics of the ORCPT parameter 205 are defined in Section 4.2 of RFC 3461 [RFC3461]. 207 ret - Match the return of content, or RET, value given in the SMTP 208 MAIL FROM command. The syntax and semantics of the RET parameter 209 are defined in Section 4.3 of RFC 3461 [RFC3461]. The possible 210 return of content values are "FULL" and "HDRS". 212 envid - Match the envelope identifier, or ENVID, value in decoded 213 form given in the SMTP MAIL FROM command. The syntax and 214 semantics of the ENVID parameter are defined in Section 4.4 of RFC 215 3461 [RFC3461]. 217 The envelope test fails unconditionally for each of these envelope- 218 part strings if the specified envelope parameter does not exist for 219 the current message or recipient. 221 The envelope test's ADDRESS-PART argument assumes the string being 222 tested has the syntax of an email address. None of the new envelope 223 parts defined here have address syntax, accordingly, it is an error 224 to specify an ADDRESS-PART argument in conjunction with these new 225 envelope parts. 227 The "relational" extension [RFC5231] adds a match type called 228 ":count". The count of an envelope test with an envelope-part of 229 "orcpt", "ret", and "envid" is 1 if the corresponding SMTP parameter 230 is present and 0 otherwise. The count of an envelope test with an 231 envelope-part of "notify" is equal to the number of notification 232 conditions specified and 0 if the NOTIFY parameter is not present. 234 4.1. Examples 236 The fact that the NOTIFY envelope parameter is multivalued and the 237 notify envelope-part turns this into a list of values makes it easy 238 to check to see if a given value is present without having to worry 239 about other values: 241 require ["envelope", "envelope-dsn"]; 243 # Check whether SUCCESS notifications were requested, 244 # irrespective of any other requests that were made 245 if envelope "notify" "SUCCESS" 246 { 247 # do whatever 248 } 250 Checking to see if a given request is the only one present is a 251 little trickier, however: 253 require ["envelope", "envelope-dsn", "relational", 254 "comparator-i;ascii-numeric"]; 256 # Check whether only FAILURE notifications were requested 257 if allof ( envelope "notify" "FAILURE", 258 envelope :comparator "i;ascii-numeric" 259 :count "eq" "notify" "1" 260 ) 261 { 262 # do whatever 263 } 265 The orcpt envelope-part always contains an address type indicator 266 prefix in addition to an address, which must be taken into account in 267 any tests: 269 require ["envelope", "envelope-dsn"]; 271 # See if the orcpt is an RFC822 address in the example.com 272 # domain 273 if envelope :matches "orcpt" "rfc822;*@example.com" 274 { 275 # do whatever 276 } 278 5. Envelope-deliverby Extension 280 The "envelope-deliverby" extension does not define any new tests or 281 actions, rather, it adds four values to the list of possible (case- 282 insensitive) envelope-part strings defined in Section 5.4 of 283 [RFC5228] and an optional :zone tagged argument. This updates the 284 usage description for envelope to: 286 Usage: envelope [COMPARATOR] [ADDRESS-PART] 287 [MATCH-TYPE] [:zone ] 288 289 291 These new envelope parts correspond to the new MAIL FROM parameters 292 defined in Section 4 of [RFC2852]. They are: 294 bytimeabsolute - Match the current value of the initial integer part 295 of the deliver-by extension's BY parameter on the SMTP MAIL FROM 296 command, converted into an absolute time represented in restricted 297 ISO 8601 format. The restricted ISO 8601 format is specified by 298 the date-time ABNF production given in [RFC3339], Section 5.6, 299 with the added restrictions that the letters "T" and "Z" MUST be 300 in upper case, and a time zone offset of zero MUST be represented 301 by "Z" and not "+00:00". 303 bytimerelative - Match the current value of the initial integer part 304 of the deliver-by extension's BY parameter specified in the SMTP 305 MAIL FROM command. 307 bymode - Match a string computed from the by-mode part of the 308 deliver-by extension's BY parameter. The possible values are 309 "notify" and "return", which correspond to the BY parameter mode 310 specifier characters "N" and "R" respectively. 312 bytrace - Match the trace modifier computed from the by-trace 313 modifier on the deliver-by extension's BY parameter. The possible 314 values are "trace" and "" (the empty string). These values 315 correspond to the presence or absence of the by-trace "T" modifier 316 respectively. 318 The envelope test fails unconditionally for each of these envelope- 319 part strings if the BY SMTP MAIL FROM parameter does not exist for 320 the current message or recipient. 322 The new :zone argument specifies a time zone offset string that any 323 bytimeabsolute value is to be shifted to prior to testing. :zone has 324 no effect on envelope-parts other than bytimeabsolute. The value of 325 time zone offset string MUST be an offset relative to UTC with the 326 following syntax: 328 time-zone = ( "+" / "-" ) 4DIGIT 330 The "+" or "-" indicates whether the time-of-day is ahead of (i.e., 331 east of) or behind (i.e., west of) UTC. The first two digits 332 indicate the number of hours difference from Universal Time, and the 333 last two digits indicate the number of minutes difference from 334 Universal Time. Note that this agrees with the RFC 2822 format for 335 time zone offsets, not the ISO 8601 format. The local time zone MUST 336 be used for bytimeabsolute if the :zone argument is omitted. 338 The envelope test's ADDRESS-PART argument assumes the string being 339 tested has the syntax of an email address. None of the new envelope 340 parts defined here have address syntax, accordingly, it is an error 341 to specify an ADDRESS-PART argument in conjunction with these new 342 envelope parts. 344 The "relational" extension [RFC5231] adds a match type called 345 ":count". The count of an envelope test with an envelope-part of 346 "bytime", "bymode", and "bytrace" is 1 if the BY parameter is present 347 and 0 otherwise. 349 It is important to note that the deliver-by by-time is decremented as 350 the message passes through the transport infrastructure. 351 Accordingly, it is not possible to tell what the message originator 352 set the value to, only the amount of time remaining at the moment the 353 sieve is run. Additionally, note that bytimerelative values can be 354 negative, making it necessary to either perform additional checks or 355 else use a comparator which, unlike i;ascii-numeric, is capable of 356 handling signed integers. 358 5.1. Examples 360 As noted above, this extension does not provide access to the 361 originator's initial by-time setting for the simple reason that this 362 information is not part of the envelope. It can, however, be used to 363 check and see if the message was delivered within the allotted time. 365 Note the additional check to see if the value is negative. 367 require ["envelope", "envelope-deliverby", "relational", 368 "comparator-i;ascii-numeric"]; 370 # Check to see if this message didn't make it in the time alloted by 371 # the originator. 372 if anyof (envelope :contains "bytimerelative" "-", 373 envelope :value "eq" :comparator "i;ascii-numeric" 374 "bytimerelative" "0") 375 { 376 # do whatever 377 } 379 This operation can be done more simply if the date [RFC5270] and 380 variables [RFC5229] extensions are available: 382 require ["envelope", "envelope-deliverby", "relational", "date", 383 "variables"]; 385 # Check to see if this message didn't make it in the time alloted by 386 # the originator. 387 if currentdate :matches "iso8601" "*" { 388 set "cdate" "${0}"; 389 if envelope :value "ge" "bytimeabsolute" "${cdate}" { 390 # do whatever 391 } 392 } 394 Note that there is no need to force the use of a particular time zone 395 since both currentdate and and the bytimeabsolute value are required 396 to default to the local time zone. A similar check could be written 397 using :zone if the action taken depends on the time 399 require ["envelope", "envelope-deliverby", "relational", "date", 400 "variables"]; 402 # If the message didn't make it in time file it according to when it 403 # should have been received 404 if envelope :matches :zone "+0000" "bytimeabolute "*T*:*:*" { 405 set "bdate" "${0}"; 406 set "bhour" "${2}"; 407 if currentdate :zone "+0000" :value "lt" "iso8601" "${bdate}") 408 fileinto "missed-${bhour}"; 409 } 410 } 412 6. redirect-dsn extension 414 The "redirect-dsn" extension does not define any new tests or 415 actions, rather, it adds two new arguments, NOTIFY and RET, to the 416 redirect action defined in Section 4.2 of [RFC5228]. This updates 417 the usage description for redirect to: 419 Usage: redirect [:notify "value"] [:ret "FULL"|"HDRS"] 420 422 The syntax for the NOTIFY and RET arguments are: 424 NOTIFY = ":notify" notify-value 425 notify-value = DQUOTE ("NEVER" / notify-esmtp-list) DQUOTE 426 notify-esmtp-list = notify-list-element *("," notify-list-element) 428 RET = ":ret" ret-value 429 ret-value = DQUOTE ("FULL" / "HDRS") DQUOTE 431 The notify-list-element production is defined in Section 4.1 of 432 [RFC3461]. 434 When these arguments are specified, they set the corresponding NOTIFY 435 ESMTP RCPT TO and RET ESMTP MAIL FROM parameters, respectively. 436 These arguments are only honored if the delivery status notification 437 (DSN) ESMTP extension is available. When the DSN extension is not 438 available, these arguments MUST be ignored and MUST NOT cause an 439 error. 441 6.1. MAIL FROM address selection 443 RFC 5228 does not require any particular envelope sender address be 444 associated with redirected messages. However, the redirect-dsn 445 extension isn't terribly useful if the place where the delivery 446 status notifications are sent isn't known. Accordingly, when either 447 :notify or :ret is specified and the envelope sender address isn't 448 empty, implementations MUST set the envelope sender address to the 449 address of the sieve owner. 451 6.2. Example 453 One possible use of :notify on redirect is to combine the copy 454 extension [RFC3894] with the ability to suppress nondelivery 455 notifications to generate a private copy of selected messages with no 456 side effects or error notifications: 458 require ["copy", "redirect-dsn"]; 460 # Make a private copy of messages from user@example.com 461 if address "from" "user@example.com" 462 { 463 redirect :copy :notify "NEVER" "elsewhere@example.com"; 464 } 466 7. redirect-deliverby extension 468 The "redirect-deliverby" extension does not define any new tests or 469 actions, rather, it adds three new arguments, BYTIME, BYMODE, and 470 BYTRACE, to the redirect action defined in Section 4.2 of [RFC5228]. 471 This updates the usage description for redirect to: 473 Usage: redirect [:bytimerelative / 474 :bytimeabsolute 475 [:bymode "notify"|"return"] [:bytrace]] 476 478 :bytimerelative specifies the number of seconds within which the 479 message should be delivered. This parameter does not allow 480 specification of negative values; it should not be necessary specify 481 such values in this context. :bytimeabsolute specifies an absolute 482 time limit on delivery. The limit in this case is specified in the 483 restricted ISO 8601 format specified by the date-time ABN production 484 given in [RFC3339] 486 :bymode specifies whether a notification should be sent or the 487 message simply returned if the time limit is exceeded. The default 488 is "return" if :bymode is not specified. :bytrace, if specified, 489 activates message tracing. 491 The semantics of delivery time limits and these parameters are 492 specified and discussed at length in [RFC2852]. 494 It is an error to specify either :bymode or :bytrace without either 495 :bytimeabsolute or :bytimerelative. 497 When these arguments are specified, they are used to construct the 498 corresponding BY ESMTP MAIL FROM parameter. The :bytimeabsolute or 499 :bytimerelative value becomes the by-time, the :bymode becomes the 500 by-mode value, and :bytrace sets the by-trace modifier. If the 501 deliver-by extension is unavailable, the handling of the redirected 502 message MUST conform to the semantics specified in [RFC2852] section 503 4.1.4 for relaying to a server that does not support the deliver-by 504 SMTP extension. 506 7.1. MAIL FROM address selection 508 RFC 5228 does not require any particular envelope sender address be 509 associated with redirected messages. However, the redirect-deliverby 510 extension, like the redirect-dsn extension, isn't terribly useful if 511 the place where any delivery status notifications are sent isn't 512 known. Accordingly, when either :bytimeabsolute or :bytimerelative 513 is specified and the envelope sender address isn't empty, 514 implementations MUST set the envelope sender address to the address 515 of the sieve owner. 517 7.2. Example 519 The obvious use of "redirect-deliverby" is to specify a limit on 520 delivery attempts for a redirected message: 522 require ["copy", "redirect-deliverby"]; 524 # Send a copy to my cell phone, time out after 10 minutes 525 if address "from" "user@example.com" 526 { 527 redirect :copy :bytimerelative 600 "cellphone@example.com"; 528 } 530 Limits on delivery after a particular time of day may also be 531 constructed: 533 require ["copy", "redirect-deliverby", "date", "variables", 534 "relational", "comparator-i;ascii-numeric"]; 536 # Send a copy to my cell phone to be delivered before 10PM 537 if currentdate :value "lt" 538 :comparator "i;ascii-numeric" "hour" "22" 539 { 540 if currentdate :matches "date" "*" {set "date" "${0}";} 541 if currentdate :matches "zone" "*" {set "zone" "${0}";} 542 redirect :copy :bytimeabsolute "${date}T20:00:00${zone}" 543 :bymode "return" "cellphone@example.com"; 544 } 546 8. Security Considerations 548 The envelope-dsn and envelope-deliverby extensions provide access to 549 additional message envelope information. This is not believed to 550 raise any additional security issues beyond those for the Sieve 551 "envelope" test. 553 The redirect-dsn extension allows specification of the delivery 554 status notification's NOTIFY parameter which can cause the generation 555 of notification messages that might otherwise not be generated, 556 especially if notification in the event of successful delivery is 557 required. Sites which limit the ability to request success 558 notifications will also need to restrict the ability to request them 559 using the redirect-dsn extension. 561 Similarly, the redirect-deliverby extension is used to control how 562 long the transport infrastructure will continue to attempt to deliver 563 a message before giving up, which could result in the generation of 564 additional notification messages. While the underlying Deliver-By 565 extension does have a minimum by-time limit, sites may wish to impose 566 additional limits on the minimum by-time allowed in a redirect 567 action. 569 All of the security considerations given in the base Sieve 570 specification also apply to this extension. 572 9. IANA Considerations 574 The following template specifies the IANA registration of the Sieve 575 extension specified in this document: 577 To: iana@iana.org 578 Subject: Registration of new Sieve extensions 580 Capability name: envelope-dsn 581 Description: The "envelope-dsn" extension extends the envelope 582 test to allow checking of information associated 583 with the DSN ESMTP extension defined in RFC 3461. 584 RFC number: RFC XXXX 585 Contact address: Sieve discussion list 587 Capability name: envelope-deliverby 588 Description: The "envelope-deliverby" extension extends the 589 envelope test to allow checking of information 590 associated with the Deliver-By ESMTP extension 591 defined in RFC 2852. 592 RFC number: RFC XXXX 593 Contact address: Sieve discussion list 595 Capability name: redirect-dsn 596 Description: The "redirect-dsn" extension extends the redirect 597 action to allow specification of the NOTIFY and 598 RET ESMTP parameters associated with the DSN SMTP 599 extension defined in RFC 3461. 600 RFC number: RFC XXXX 601 Contact address: Sieve discussion list 603 Capability name: redirect-deliverby 604 Description: The "redirect-deliverby" extension extends the 605 redirect action to allow specification of the BY 606 ESMTP parameter associated with the Deliver-By SMTP 607 extension defined in RFC 2852. 608 RFC number: RFC XXXX 609 Contact address: Sieve discussion list 611 This information should be added to the list of sieve extensions 612 given on http://www.iana.org/assignments/sieve-extensions. 614 10. References 615 10.1. Normative references 617 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 618 Requirement Levels", BCP 14, RFC 2119, March 1997. 620 [RFC2852] Newman, D., "Deliver By SMTP Service Extension", RFC 2852, 621 June 2000. 623 [RFC3339] Klyne, G., Ed. and C. Newman, "Date and Time on the 624 Internet: Timestamps", RFC 3339, July 2002. 626 [RFC3461] Moore, K., "Simple Mail Transfer Protocol (SMTP) Service 627 Extension for Delivery Status Notifications (DSNs)", 628 RFC 3461, January 2003. 630 [RFC5228] Guenther, P. and T. Showalter, "Sieve: An Email Filtering 631 Language", RFC 5228, January 2008. 633 [RFC5231] Segmuller, W. and B. Leiba, "Sieve Email Filtering: 634 Relational Extension", RFC 5231, January 2008. 636 [RFC5234] Crocker, D. and P. Overell, "Augmented BNF for Syntax 637 Specifications: ABNF", STD 68, RFC 5234, January 2008. 639 [RFC5321] Klensin, J., "Simple Mail Transfer Protocol", RFC 5321, 640 October 2008. 642 10.2. Informative references 644 [RFC3501] Crispin, M., "INTERNET MESSAGE ACCESS PROTOCOL - VERSION 645 4rev1", RFC 3501, March 2003. 647 [RFC3894] Degener, J., "Sieve Extension: Copying Without Side 648 Effects", RFC 3894, October 2004. 650 [RFC5229] Homme, K., "Sieve Email Filtering: Variables Extension", 651 RFC 5229, January 2008. 653 [RFC5270] Jang, H., Jee, J., Han, Y., Park, S., and J. Cha, "Mobile 654 IPv6 Fast Handovers over IEEE 802.16e Networks", RFC 5270, 655 June 2008. 657 Appendix A. Acknowledgements 659 Cyrus Daboo, Derek Diget, Philip Guenther, Arnt Gulbrandsen, Tero 660 Kivinen, Barry Leiba, Andrew McKeon, Alexey Melnikov, Chris Newman, 661 Aaron Stone, and Alexandros Vellis provided helpful suggestions and 662 corrections. 664 Author's Address 666 Ned Freed 667 Oracle 668 800 Royal Oaks 669 Monrovia, CA 91016-6347 670 USA 672 Email: ned.freed@mrochek.com