idnits 2.17.1 draft-ietf-extra-sieve-fcc-09.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. 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 the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords -- however, there's a paragraph with a matching beginning. Boilerplate error? (The document does seem to have the reference to RFC 2119 which the ID-Checklist requires). (Using the creation date from RFC5230, updated by this document, for RFC5378 checks: 2005-03-16) -- 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 (January 13, 2019) is 1923 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) -- Looks like a reference, but probably isn't: '1' on line 577 == Missing Reference: 'FCC' is mentioned on line 283, but not defined -- Looks like a reference, but probably isn't: '2' on line 579 -- Looks like a reference, but probably isn't: '3' on line 581 -- Looks like a reference, but probably isn't: '4' on line 583 == Outdated reference: A later version (-05) exists of draft-ietf-extra-sieve-special-use-04 Summary: 0 errors (**), 0 flaws (~~), 4 warnings (==), 6 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 EXTRA K. Murchison 3 Internet-Draft B. Gondwana 4 Updates: 5230, 5435 (if approved) FastMail 5 Intended status: Standards Track January 13, 2019 6 Expires: July 17, 2019 8 Sieve Extension: File Carbon Copy (Fcc) 9 draft-ietf-extra-sieve-fcc-09 11 Abstract 13 The Sieve Email Filtering Language provides a number of action 14 commands, some of which can generate additional messages on behalf of 15 the user. This document defines an extension to such commands to 16 allow a copy of any generated message to be filed into a target 17 mailbox. 19 This document updates RFC5230 and RFC5435 by adding a new tagged 20 argument to the "vacation" and "enotify" actions respectively. 22 Status of This Memo 24 This Internet-Draft is submitted in full conformance with the 25 provisions of BCP 78 and BCP 79. 27 Internet-Drafts are working documents of the Internet Engineering 28 Task Force (IETF). Note that other groups may also distribute 29 working documents as Internet-Drafts. The list of current Internet- 30 Drafts is at https://datatracker.ietf.org/drafts/current/. 32 Internet-Drafts are draft documents valid for a maximum of six months 33 and may be updated, replaced, or obsoleted by other documents at any 34 time. It is inappropriate to use Internet-Drafts as reference 35 material or to cite them other than as "work in progress." 37 This Internet-Draft will expire on July 17, 2019. 39 Copyright Notice 41 Copyright (c) 2019 IETF Trust and the persons identified as the 42 document authors. All rights reserved. 44 This document is subject to BCP 78 and the IETF Trust's Legal 45 Provisions Relating to IETF Documents 46 (https://trustee.ietf.org/license-info) in effect on the date of 47 publication of this document. Please review these documents 48 carefully, as they describe your rights and restrictions with respect 49 to this document. Code Components extracted from this document must 50 include Simplified BSD License text as described in Section 4.e of 51 the Trust Legal Provisions and are provided without warranty as 52 described in the Simplified BSD License. 54 Table of Contents 56 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 57 2. Conventions Used in This Document . . . . . . . . . . . . . . 3 58 3. Tagged Argument ":fcc" . . . . . . . . . . . . . . . . . . . 3 59 3.1. Interaction with Fileinto Extensions . . . . . . . . . . 3 60 3.1.1. Imap4flags Extension . . . . . . . . . . . . . . . . 4 61 3.1.2. Mailbox Extension . . . . . . . . . . . . . . . . . . 4 62 3.1.3. Special-Use Extension . . . . . . . . . . . . . . . . 4 63 3.2. Collected Grammar . . . . . . . . . . . . . . . . . . . . 5 64 4. Format of File Carbon Copied Messages . . . . . . . . . . . . 5 65 5. Interaction with the Vacation Action . . . . . . . . . . . . 6 66 6. Interaction with the Notify Action . . . . . . . . . . . . . 6 67 6.1. Notification-Capability "fcc" . . . . . . . . . . . . . . 7 68 7. Compatibility with the Reject and Extended Reject 69 Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 70 8. Compatibility with Other Actions . . . . . . . . . . . . . . 8 71 9. Implementation Status . . . . . . . . . . . . . . . . . . . . 8 72 10. Security Considerations . . . . . . . . . . . . . . . . . . . 9 73 11. Privacy Considerations . . . . . . . . . . . . . . . . . . . 9 74 12. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10 75 12.1. Registration of Sieve Extension . . . . . . . . . . . . 10 76 12.2. Registration of Notification-Capability 77 Parameter . . . . . . . . . . . . . . . . . . . . . . . 10 78 13. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 10 79 14. References . . . . . . . . . . . . . . . . . . . . . . . . . 11 80 14.1. Normative References . . . . . . . . . . . . . . . . . . 11 81 14.2. Informative References . . . . . . . . . . . . . . . . . 12 82 14.3. URIs . . . . . . . . . . . . . . . . . . . . . . . . . . 13 83 Appendix A. Change History (To be removed by RFC Editor before 84 publication) . . . . . . . . . . . . . . . . . . . . 13 85 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 15 87 1. Introduction 89 The Sieve Email Filtering Language [RFC5228] provides a number of 90 action commands, some of which can generate additional messages on 91 behalf of the user. It is sometimes desirable for a Sieve user to 92 maintain an archive of the messages generated by these commands. 94 This extension defines a new optional tagged argument ":fcc" to 95 action commands that generate additional messages to allow a copy of 96 the generated message to be filed into a target mailbox. 98 The capability string associated with this extension is "fcc". 100 Each new action that generates additional messages will need to 101 specify how it interacts with :fcc. This document specifies the 102 interaction of :fcc with the Vacation [RFC5230] and Notify [RFC5435] 103 extensions. 105 2. Conventions Used in This Document 107 Conventions for notations are as in Section 1.1 of [RFC5228], 108 including use of the "Usage:" label for the definition of action and 109 tagged arguments syntax. 111 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 112 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 113 "OPTIONAL" in this document are to be interpreted as described in BCP 114 14 [1] [RFC2119] [RFC8174] when, and only when, they appear in all 115 capitals, as shown here. 117 3. Tagged Argument ":fcc" 119 This document specifies a new optional tagged argument ":fcc" that 120 alters the behavior of action commands that generate additional 121 messages on behalf of the user. 123 Usage: :fcc 125 The :fcc tagged argument instructs the Sieve interpreter to file a 126 copy of the generated message into the mailbox provided in the 127 subsequent argument. The semantics and treatment of the mailbox 128 argument are defined to match those of the mailbox argument to the 129 "fileinto" action specified in Section 4.1 of [RFC5228]. 130 Specifically, use of an invalid mailbox name MAY be treated as an 131 error or result in delivery to an implementation-defined mailbox, and 132 if the specified mailbox doesn't exist, the implementation MAY treat 133 it as an error, create the mailbox, or file the message into an 134 implementation-defined mailbox. 136 3.1. Interaction with Fileinto Extensions 138 Some tagged arguments defined in extensions to the "fileinto" action 139 can be used together with ":fcc". The sections below describe these 140 interactions. Tagged arguments in future extensions to the 141 "fileinto" action need to describe their interaction with ":fcc", if 142 any. 144 When any "fileinto" extension arguments are used with ":fcc", the 145 corresponding extension MUST be enabled, and the arguments are 146 defined to have the same syntax, semantics, and treatment as they do 147 with "fileinto". 149 3.1.1. Imap4flags Extension 151 This document extends the definition of the ":flags" tagged argument 152 (see Section 5 of [RFC5232]) so that it can optionally be used with 153 the ":fcc" argument. 155 Usage: :fcc [:flags ] 157 If the optional ":flags" argument is specified with ":fcc", it 158 instructs the Sieve interpreter to set the IMAP4 flags provided in 159 the subsequent argument when the generated message is filed into the 160 target mailbox. 162 3.1.2. Mailbox Extension 164 This document extends the definition of the ":create" tagged argument 165 (see Section 3.2 of [RFC5490]) so that it can optionally be used with 166 the ":fcc" argument. 168 Usage: :fcc [:create] 170 If the optional ":create" argument is specified with ":fcc", it 171 instructs the Sieve interpreter to create the target mailbox, if 172 needed, before attempting to file the generated message into the 173 target mailbox. 175 3.1.3. Special-Use Extension 177 This document extends the definition of the ":specialuse" tagged 178 argument (see Section 4 of [I-D.ietf-extra-sieve-special-use]) so 179 that it can optionally be used with the ":fcc" argument. 181 Usage: :fcc [:specialuse ] 183 If the optional ":specialuse" argument is specified with ":fcc", it 184 instructs the Sieve interpreter to check whether a mailbox exists 185 with the specific special-use flag assigned to it. If such a mailbox 186 exists, the generated message is filed into the special-use mailbox. 187 Otherwise, the generated message is filed into the target mailbox. 189 If both the optional ":specialuse" and ":create" arguments are 190 specified with ":fcc", the Sieve interpreter is instructed to create 191 the target mailbox per Section 4.1 of 192 [I-D.ietf-extra-sieve-special-use], if needed. 194 3.2. Collected Grammar 196 For convenience, the "FCC" syntax element is defined here using ABNF 197 [RFC5234] so that it can be augmented by other extensions. 199 Note that the following is the grammar of "FCC" after it has been 200 lexically interpreted. No whitespace or comments appear below. 202 FCC = ":fcc" string *FCC-OPTS 203 ; per Section 2.6.2 of RFC5228, 204 ; the tagged arguments in FCC may appear in any order 206 FCC-OPTS = CREATE / IMAP-FLAGS / SPECIAL-USE 207 ; each option MUST NOT appear more than once 209 CREATE = ":create" 210 IMAP-FLAGS = ":flags" string-list 211 SPECIAL-USE = ":specialuse" string 213 4. Format of File Carbon Copied Messages 215 Copies of messages filed into a mailbox via this extension are 216 REQUIRED to be in Internet Message Format [RFC5322]. Some messages 217 generated by Sieve actions might already conform to this format and 218 MAY be filed without modification. Messages generated in other 219 formats MUST be encapsulated using constructs from [RFC5322] and MIME 220 ([RFC2045], [RFC2046], [RFC2047], [RFC2231]). 222 The general requirements for encapsulating the copies of messages to 223 be filed are the following: 225 o Date: The Date header field is REQUIRED and SHOULD be set to the 226 date and time when the message was generated. 228 o From: The From header field is REQUIRED and SHOULD be set to the 229 email address of the owner of the Sieve script, unless explicitly 230 overridden by rules for encapsulating a particular message type. 232 o To: The To header field is OPTIONAL and MAY be set to the email 233 address of the recipient of the generated message, if available. 235 o Subject: The Subject header field is OPTIONAL and MAY be generated 236 as follows: The subject is set to the characters "Fcc: " followed 237 by the subject of the message being processed by the Sieve 238 interpreter. 240 o In-Reply-To: The In-Reply-To header field is OPTIONAL and MAY be 241 set to the Message-ID of the message being processed by the Sieve 242 interpreter. 244 o Message Body: The body of the filed message is REQUIRED and is 245 composed of one or more MIME-parts containing the generated 246 message and any related metadata. The Content-Type header 247 field(s) MUST be set to the appropriate MIME types. If any of the 248 MIME-parts include 8-bit or binary data, the Content-Transfer- 249 Encoding header field(s) MUST be set accordingly. 251 5. Interaction with the Vacation Action 253 This document extends the "vacation" [RFC5230] action (see also 254 "vacation-seconds" [RFC6131]) to optionally store a copy of the auto- 255 reply messages into a target mailbox. 257 Usage: vacation [FCC] 258 [":days" number | ":seconds" number] 259 [":subject" string] 260 [":from" string] 261 [":addresses" string-list] 262 [":mime"] 263 [":handle" string] 264 266 Example (with fileinto extensions): 268 require ["vacation", "fcc", "mailbox", "special-use", "imap4flags"]; 270 vacation :days 7 271 :from "hemingway@example.com" "Gone Fishin'" 272 :specialuse "\\Sent" :create 273 :fcc "INBOX.Sent" :flags ["\\Seen"]; 275 Vacation auto-reply messages are MIME-compliant and can be filed into 276 the target mailbox without modification. 278 6. Interaction with the Notify Action 280 This document extends the "notify" [RFC5435] action to optionally 281 store a copy of the notification messages into a target mailbox. 283 Usage: notify [FCC] 284 [":from" string] 285 [":importance" <"1" / "2" / "3">] 286 [":options" string-list] 287 [":message" string] 288 290 Example: 292 require ["enotify", "fcc"]; 294 notify :fcc "INBOX.Sent" 295 :message "You got mail!" 296 "mailto:ken@example.com"; 298 Messages generated using the "mailto" [RFC5436] notification method 299 are MIME-compliant and can be filed into the target mailbox without 300 modification. 302 Messages generated by other notification methods (e.g. "xmpp" 303 [RFC5437]) MUST be encapsulated per Section 4 before being filed. 304 The body of the filed message MUST include the :message parameter and 305 MAY include one or more of the :from, :importance, or :options 306 parameters. The MIME-type(s) of the body part(s) used to encapsulate 307 the parameters is an implementation decision. 309 An implementation MAY only support :fcc in conjunction with a subset 310 of the notification methods it supports. An error occurs if :fcc is 311 combined with a notification method that doesn't support it. 312 Notification methods that support :fcc can be discovered at run-time 313 using the mechanism described below (Section 6.1). 315 6.1. Notification-Capability "fcc" 317 This document defines a new notification-capability value "fcc" for 318 use with the notify_method_capability test (see Section 5 of 319 [RFC5435]. For the "fcc" notification-capability, the 320 notify_method_capability test can match one of the following key-list 321 values: 323 yes A copy of the notification message sent using the method 324 identified by the notification-uri can be filed into a target 325 mailbox. 327 no A copy of the notification message sent using the method 328 identified by the notification-uri can not be filed into a target 329 mailbox. 331 Note that the "fcc" notify_method_capability test does not require 332 the notification-uri argument to specify anything other than a 333 scheme. 335 Example: 337 require ["enotify", "fcc"]; 339 if notify_method_capability "xmpp:" "fcc" "yes" { 340 notify :fcc "INBOX.Sent" 341 :message "You got mail" 342 "xmpp:ken@example.com?message;subject=SIEVE"; 343 } else { 344 notify :fcc "INBOX.Sent" 345 :message "You got mail!" 346 "mailto:ken@example.com"; 347 } 349 7. Compatibility with the Reject and Extended Reject Actions 351 Implementations MUST NOT allow use of "fcc" with the "reject" and 352 "ereject" [RFC5429] actions. Allowing "fcc" with these actions would 353 violate the SMTP [RFC5321] principle that a message is either 354 delivered or bounced back to the sender. Namely, the saved copy of 355 the rejection message will contain the original message. 357 It is an error for a script to use the ":fcc" tagged argument with 358 either "reject" or "ereject". 360 8. Compatibility with Other Actions 362 The "fcc" extension is not compatible with any Sieve action that does 363 not generate an additional message on behalf of the user. It is an 364 error for a script to use the ":fcc" tagged argument with any such 365 action. 367 Future extensions that define actions that generate additional 368 messages on behalf of the user need to describe their compatibility 369 with ":fcc", and how to MIME-encapsulate the message, if required. 371 9. Implementation Status 373 < RFC Editor: before publication please remove this section and the 374 reference to [RFC7942] > 376 This section records the status of known implementations of the 377 protocol defined by this specification at the time of posting of this 378 Internet-Draft, and is based on a proposal described in [RFC7942]. 380 The description of implementations in this section is intended to 381 assist the IETF in its decision processes in progressing drafts to 382 RFCs. Please note that the listing of any individual implementation 383 here does not imply endorsement by the IETF. Furthermore, no effort 384 has been spent to verify the information presented here that was 385 supplied by IETF contributors. This is not intended as, and must not 386 be construed to be, a catalog of available implementations or their 387 features. Readers are advised to note that other implementations may 388 exist. 390 According to [RFC7942], "this will allow reviewers and working groups 391 to assign due consideration to documents that have the benefit of 392 running code, which may serve as evidence of valuable experimentation 393 and feedback that have made the implemented protocols more mature. 394 It is up to the individual working groups to use this information as 395 they see fit". 397 9.1. Cyrus Server 399 The open source Cyrus Server [2] project is a highly scalable 400 enterprise mail system which supports Sieve email filtering at the 401 point of final delivery. This production level Sieve implementation 402 supports all of the requirements described in this document. This 403 implementation is freely distributable under a BSD style license from 404 Computing Services at Carnegie Mellon University [3]. 406 9.2. Oracle Communications Messaging Server 408 The Oracle Communications Messaging Server [4] is a highly scalable, 409 reliable, and available messaging platform. This production level 410 product supports the :fcc extension in conjunction with both the 411 notify and vacation extensions. The implementation meets all the 412 requirements given in this document. The product also supports the 413 imap4flags extension so the :flags may be used in conjunction :fcc. 415 10. Security Considerations 417 In addition to the security considerations in [RFC5228], [RFC5230], 418 [RFC5435], and [RFC6131], it should be noted that filing copies of 419 generated messages may cause the Sieve script owner to exceed their 420 allocated storage (quota) on the mail system, thereby preventing 421 delivery of future messages destined for the owner. 423 11. Privacy Considerations 425 In addition to the privacy considerations in [RFC5228], [RFC5230], 426 [RFC5435], and [RFC6131], it should be noted that a copy of a 427 generated message filed into a shared or public maibox (as opposed to 428 a private mailbox) could expose private information about the Sieve 429 script owner to third parties. For instance, users that have access 430 to the shared/public mailbox might discover that the Sieve script 431 owner is on holiday or might discover the owner's physical location. 433 12. IANA Considerations 435 12.1. Registration of Sieve Extension 437 To: iana@iana.org 439 Subject: Registration of new Sieve extension 441 Capability name: fcc 443 Description: Adds the ":fcc" parameter to Sieve action commands 444 that generate additional messages. 446 RFC number: RFC XXXX 448 Contact address: The Sieve discussion list 450 12.2. Registration of Notification-Capability Parameter 452 To: iana@iana.org 454 Subject: Registration of a new notification-capability parameter 456 Capability name: fcc 458 Description: Returns whether a copy of the notification message 459 sent using the method identified by the notification-uri parameter 460 to the notify_method_capability test can be filed into a target 461 mailbox. 463 Syntax: Can contain one of two values: "yes" or "no". Values MUST 464 be in lowercase. 466 Permanent and readily available reference(s): This RFC 468 Contact information: The Sieve discussion list 471 13. Acknowledgments 473 The authors would like to thank the following individuals for 474 contributing their ideas and support for writing this specification: 475 Ned Freed, Stan Kalisch, and Alexey Melnikov. 477 14. References 479 14.1. Normative References 481 [I-D.ietf-extra-sieve-special-use] 482 Bosch, S., "Sieve Email Filtering: Delivering to Special- 483 Use Mailboxes", draft-ietf-extra-sieve-special-use-04 484 (work in progress), November 2018. 486 [RFC2045] Freed, N. and N. Borenstein, "Multipurpose Internet Mail 487 Extensions (MIME) Part One: Format of Internet Message 488 Bodies", RFC 2045, DOI 10.17487/RFC2045, November 1996, 489 . 491 [RFC2046] Freed, N. and N. Borenstein, "Multipurpose Internet Mail 492 Extensions (MIME) Part Two: Media Types", RFC 2046, 493 DOI 10.17487/RFC2046, November 1996, 494 . 496 [RFC2047] Moore, K., "MIME (Multipurpose Internet Mail Extensions) 497 Part Three: Message Header Extensions for Non-ASCII Text", 498 RFC 2047, DOI 10.17487/RFC2047, November 1996, 499 . 501 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 502 Requirement Levels", BCP 14, RFC 2119, 503 DOI 10.17487/RFC2119, March 1997, 504 . 506 [RFC2231] Freed, N. and K. Moore, "MIME Parameter Value and Encoded 507 Word Extensions: Character Sets, Languages, and 508 Continuations", RFC 2231, DOI 10.17487/RFC2231, November 509 1997, . 511 [RFC5228] Guenther, P., Ed. and T. Showalter, Ed., "Sieve: An Email 512 Filtering Language", RFC 5228, DOI 10.17487/RFC5228, 513 January 2008, . 515 [RFC5230] Showalter, T. and N. Freed, Ed., "Sieve Email Filtering: 516 Vacation Extension", RFC 5230, DOI 10.17487/RFC5230, 517 January 2008, . 519 [RFC5232] Melnikov, A., "Sieve Email Filtering: Imap4flags 520 Extension", RFC 5232, DOI 10.17487/RFC5232, January 2008, 521 . 523 [RFC5234] Crocker, D., Ed. and P. Overell, "Augmented BNF for Syntax 524 Specifications: ABNF", STD 68, RFC 5234, 525 DOI 10.17487/RFC5234, January 2008, 526 . 528 [RFC5322] Resnick, P., Ed., "Internet Message Format", RFC 5322, 529 DOI 10.17487/RFC5322, October 2008, 530 . 532 [RFC5429] Stone, A., Ed., "Sieve Email Filtering: Reject and 533 Extended Reject Extensions", RFC 5429, 534 DOI 10.17487/RFC5429, March 2009, 535 . 537 [RFC5435] Melnikov, A., Ed., Leiba, B., Ed., Segmuller, W., and T. 538 Martin, "Sieve Email Filtering: Extension for 539 Notifications", RFC 5435, DOI 10.17487/RFC5435, January 540 2009, . 542 [RFC5490] Melnikov, A., "The Sieve Mail-Filtering Language -- 543 Extensions for Checking Mailbox Status and Accessing 544 Mailbox Metadata", RFC 5490, DOI 10.17487/RFC5490, March 545 2009, . 547 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 548 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 549 May 2017, . 551 14.2. Informative References 553 [RFC5321] Klensin, J., "Simple Mail Transfer Protocol", RFC 5321, 554 DOI 10.17487/RFC5321, October 2008, 555 . 557 [RFC5436] Leiba, B. and M. Haardt, "Sieve Notification Mechanism: 558 mailto", RFC 5436, DOI 10.17487/RFC5436, January 2009, 559 . 561 [RFC5437] Saint-Andre, P. and A. Melnikov, "Sieve Notification 562 Mechanism: Extensible Messaging and Presence Protocol 563 (XMPP)", RFC 5437, DOI 10.17487/RFC5437, January 2009, 564 . 566 [RFC6131] George, R. and B. Leiba, "Sieve Vacation Extension: 567 "Seconds" Parameter", RFC 6131, DOI 10.17487/RFC6131, July 568 2011, . 570 [RFC7942] Sheffer, Y. and A. Farrel, "Improving Awareness of Running 571 Code: The Implementation Status Section", BCP 205, 572 RFC 7942, DOI 10.17487/RFC7942, July 2016, 573 . 575 14.3. URIs 577 [1] https://tools.ietf.org/html/bcp14 579 [2] http://www.cyrusimap.org/ 581 [3] http://www.cmu.edu/computing/ 583 [4] https://www.oracle.com/industries/communications/enterprise/ 584 products/messaging-server/index.html 586 Appendix A. Change History (To be removed by RFC Editor before 587 publication) 589 Changes since draft-ietf-extra-sieve-fcc-08: 591 o Introduced additional security and privacy considerations. 593 o Reintroduced text describing incompatibility with [e]reject. 595 o Reverted to RFC 5228 fileinto language regarding invalid/non- 596 existent FCC mailbox. 598 o Editorial changes from IESG review. 600 o Editorial changes from Gen-ART review. 602 Changes since draft-ietf-extra-sieve-fcc-07: 604 o Added comments regarding FCC ABNF per Alexey Melnikov. 606 o Reordered arguments in the "vacation" example to show ":fcc" 607 appearing amongst FCC-OPTS. 609 Changes since draft-ietf-extra-sieve-fcc-06: 611 o Reorganized sections. 613 o Switched to using proper ABNF for FCC and fileinto extensions. 615 o Fcc into INBOX if specified target mailbox doesn't exist. 617 o Editorial changes from Alexey Melnikov. 619 o Other minor editorial changes. 621 Changes since draft-ietf-extra-sieve-fcc-05: 623 o Editorial changes from Jiankang Yao. 625 Changes since draft-ietf-extra-sieve-fcc-04: 627 o Editorial changes from Ned Freed. 629 o Added information on Oracle implementation. 631 Changes since draft-ietf-extra-sieve-fcc-03: 633 o Fixed typo in ABNF. 635 Changes since draft-ietf-extra-sieve-fcc-02: 637 o Updated Keywords boilerplate. 639 o Noted that :fcc mailbox argument and any fileinto extension 640 arguments used wth :fcc have the same syntax and semantics as they 641 have with fileinto. 643 o Removed section on [e]Reject. 645 o Added "fcc" notification-capability. 647 o Added Implementation Status section. 649 o Editorial changes from Ned Freed. 651 Changes since draft-ietf-extra-sieve-fcc-01: 653 o Added text discussing how to handle generated messages that are 654 not in MIME format. 656 o Adjusted ABNF so that tagged arguments that supplement :fcc no 657 longer appear as positional. 659 Changes since draft-ietf-extra-sieve-fcc-00: 661 o Updated abstract with text from Ned. 663 o Added support for :fcc to notify extension. 665 o Prohibit use of :fcc with reject and ereject extensions. 667 o Added registration of the extension with IANA. 669 o Added Acknowledgments. 671 o Minor editorial changes. 673 Authors' Addresses 675 Kenneth Murchison 676 FastMail US LLC 677 1429 Walnut Street - Suite 1201 678 Philadelphia, PA 19102 679 USA 681 Email: murch@fastmailteam.com 683 Bron Gondwana 684 FastMail Pty Ltd 685 Level 2, 114 William Street 686 Melbourne, VIC 3000 687 Australia 689 Email: brong@fastmailteam.com