idnits 2.17.1 draft-ietf-extra-sieve-fcc-08.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 (December 4, 2018) is 1967 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 536 == Missing Reference: 'FCC' is mentioned on line 275, but not defined -- Looks like a reference, but probably isn't: '2' on line 538 -- Looks like a reference, but probably isn't: '3' on line 540 -- Looks like a reference, but probably isn't: '4' on line 542 == 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 December 4, 2018 6 Expires: June 7, 2019 8 Sieve Extension: File Carbon Copy (Fcc) 9 draft-ietf-extra-sieve-fcc-08 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 June 7, 2019. 39 Copyright Notice 41 Copyright (c) 2018 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 Other Actions . . . . . . . . . . . . . . 8 69 8. Implementation Status . . . . . . . . . . . . . . . . . . . . 8 70 9. Security Considerations . . . . . . . . . . . . . . . . . . . 9 71 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9 72 10.1. Registration of Sieve Extension . . . . . . . . . . . . 9 73 10.2. Registration of Notification-Capability 74 Parameter . . . . . . . . . . . . . . . . . . . . . . . 10 75 11. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 10 76 12. References . . . . . . . . . . . . . . . . . . . . . . . . . 10 77 12.1. Normative References . . . . . . . . . . . . . . . . . . 10 78 12.2. Informative References . . . . . . . . . . . . . . . . . 12 79 12.3. URIs . . . . . . . . . . . . . . . . . . . . . . . . . . 12 80 Appendix A. Change History (To be removed by RFC Editor before 81 publication) . . . . . . . . . . . . . . . . . . . . 12 82 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 14 84 1. Introduction 86 The Sieve Email Filtering Language [RFC5228] provides a number of 87 action commands, some of which can generate additional messages on 88 behalf of the user. It is sometimes desirable for a Sieve user to 89 maintain an archive of the messages generated by these commands. 91 This extension defines a new optional tagged argument ":fcc" to 92 action commands which generate additional messages to allow a copy of 93 the generated message to be filed into a target mailbox. 95 The capability string associated with this extension is "fcc". 97 Each action that generates additional messages will need to specify 98 how it interfacts with :fcc. This document specifies the interaction 99 of :fcc with the Vacation [RFC5230] and Notify [RFC5435] extensions. 101 2. Conventions Used in This Document 103 Conventions for notations are as in Section 1.1 of [RFC5228], 104 including use of the "Usage:" label for the definition of action and 105 tagged arguments syntax. 107 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 108 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 109 "OPTIONAL" in this document are to be interpreted as described in BCP 110 14 [1] [RFC2119] [RFC8174] when, and only when, they appear in all 111 capitals, as shown here. 113 3. Tagged Argument ":fcc" 115 This document specifies a new optional tagged argument ":fcc" that 116 alters the behavior of action commands which generate additional 117 messages on behalf of the user. 119 Usage: :fcc 121 The :fcc tagged argument instructs the Sieve interpreter to file a 122 copy of the generated message into the mailbox provided in the 123 subsequent argument. The syntax and semantics of the mailbox 124 argument MUST match those of the mailbox argument to the "fileinto" 125 action specified in Section 4.1 of [RFC5228]. If the specified 126 mailbox doesn't exist, the implementation MUST file the message into 127 the user's main mailbox (e.g. IMAP "INBOX"). 129 3.1. Interaction with Fileinto Extensions 131 Some tagged arguments defined in extensions to the "fileinto" action 132 can be used together with ":fcc". The sections below describe these 133 interactions. Tagged arguments in future extensions to the 134 "fileinto" action should describe their interaction with ":fcc", if 135 any. 137 When any "fileinto" extension arguments are used with ":fcc", the 138 corresponding extension MUST be enabled, and the arguments MUST have 139 the same syntax and semantics as they do with "fileinto". 141 3.1.1. Imap4flags Extension 143 This document extends the definition of the ":flags" tagged argument 144 (see Section 5 of [RFC5232]) so that it can optionally be used with 145 the ":fcc" argument. 147 Usage: :fcc [:flags ] 149 If the optional ":flags" argument is specified with ":fcc", it 150 instructs the Sieve interpreter to set the IMAP4 flags provided in 151 the subsequent argument when the generated message is filed into the 152 target mailbox. 154 3.1.2. Mailbox Extension 156 This document extends the definition of the ":create" tagged argument 157 (see Section 3.2 of [RFC5490]) so that it can optionally be used with 158 the ":fcc" argument. 160 Usage: :fcc [:create] 162 If the optional ":create" argument is specified with ":fcc", it 163 instructs the Sieve interpreter to create the target mailbox, if 164 needed, before attempting to file the generated message into the 165 target mailbox. 167 3.1.3. Special-Use Extension 169 This document extends the definition of the ":specialuse" tagged 170 argument (see Section 4 of [I-D.ietf-extra-sieve-special-use]) so 171 that it can optionally be used with the ":fcc" argument. 173 Usage: :fcc [:specialuse ] 175 If the optional ":specialuse" argument is specified with ":fcc", it 176 instructs the Sieve interpreter to check whether a mailbox exists 177 with the specific special-use flag assigned to it. If such a mailbox 178 exists, the generated message is filed into the special-use mailbox. 179 Otherwise, the generated message is filed into the target mailbox. 181 If both the optional ":specialuse" and ":create" arguments are 182 specified with ":fcc", the Sieve interpreter is instructed to create 183 the target mailbox per Section 4.1 of 184 [I-D.ietf-extra-sieve-special-use], if needed. 186 3.2. Collected Grammar 188 For convenience, the "FCC" syntax element is defined here using ABNF 189 [RFC5234] so that it can be augmented by other extensions. 191 Note that the following is the grammar of "FCC" after it has been 192 lexically interpreted. No whitespace or comments appear below. 194 FCC = ":fcc" string *FCC-OPTS 195 ; per Section 2.6.2 of RFC5228, 196 ; the tagged arguments in FCC may appear in any order 198 FCC-OPTS = CREATE / IMAP-FLAGS / SPECIAL-USE 199 ; each option MUST NOT appear more than once 201 CREATE = ":create" 202 IMAP-FLAGS = ":flags" string-list 203 SPECIAL-USE = ":specialuse" string 205 4. Format of File Carbon Copied Messages 207 Copies of messages filed into a mailbox via this extension are 208 REQUIRED to be in Internet Message Format [RFC5322]. Some messages 209 generated by Sieve actions might already conform to this format and 210 MAY be filed without modification. Messages generated in other 211 formats MUST be encapsulated using constructs from [RFC5322] and MIME 212 ([RFC2045], [RFC2046], [RFC2047], [RFC2231]). 214 The general requirements for encapsulating the copies of messages to 215 be filed are the following: 217 o Date: The Date header field is REQUIRED and SHOULD be set to the 218 date and time when the message was generated. 220 o From: The From header field is REQUIRED and SHOULD be set to the 221 email address of the owner of the Sieve script, unless explicitly 222 overridden by rules for encapsulating a particular message type. 224 o To: The To header field is OPTIONAL and MAY be set to the email 225 address of the recipient of the generated message, if available. 227 o Subject: The Subject header field is OPTIONAL and MAY be generated 228 as follows: The subject is set to the characters "Fcc: " followed 229 by the subject of the message being processed by the Sieve 230 interpreter. 232 o In-Reply-To: The In-Reply-To header field is OPTIONAL and MAY be 233 set to the Message-ID of the message being processed by the Sieve 234 interpreter. 236 o Message Body: The body of the filed message is REQUIRED and is 237 composed of one or more MIME-parts containing the generated 238 message and any related metadata. The Content-Type header 239 field(s) MUST be set to the appropriate MIME types. If any of the 240 MIME-parts include 8-bit or binary data, the Content-Transfer- 241 Encoding header field(s) MUST be set accordingly. 243 5. Interaction with the Vacation Action 245 This document extends the "vacation" [RFC5230] action (see also 246 "vacation-seconds" [RFC6131]) to optionally store a copy of the auto- 247 reply messages into a target mailbox. 249 Usage: vacation [FCC] 250 [":days" number | ":seconds" number] 251 [":subject" string] 252 [":from" string] 253 [":addresses" string-list] 254 [":mime"] 255 [":handle" string] 256 258 Example (with fileinto extensions): 260 require ["vacation", "fcc", "mailbox", "special-use", "imap4flags"]; 262 vacation :days 7 263 :from "hemingway@example.com" "Gone Fishin'" 264 :specialuse "\\Sent" :create 265 :fcc "INBOX.Sent" :flags ["\\Seen"]; 267 Vacation auto-reply messages are MIME-compliant and can be filed into 268 the target mailbox without modification. 270 6. Interaction with the Notify Action 272 This document extends the "notify" [RFC5435] action to optionally 273 store a copy of the notification messages into a target mailbox. 275 Usage: notify [FCC] 276 [":from" string] 277 [":importance" <"1" / "2" / "3">] 278 [":options" string-list] 279 [":message" string] 280 282 Example: 284 require ["enotify", "fcc"]; 286 notify :fcc "INBOX.Sent" 287 :message "You got mail!" 288 "mailto:ken@example.com"; 290 Messages generated using the "mailto" [RFC5436] notification method 291 are MIME-compliant and can be filed into the target mailbox without 292 modification. 294 Messages generated by other notification methods (e.g. "xmpp" 295 [RFC5437]) MUST be encapsulated per Section 4 before being filed. 296 The body of the filed message MUST include the :message parameter and 297 MAY include one or more of the :from, :importance, or :options 298 parameters. The MIME-type(s) of the body part(s) used to encapsulate 299 the parameters is an implementation decision. 301 An implementation MAY only support :fcc in conjunction with a subset 302 of the notification methods it supports. An error occurs if :fcc is 303 combined with a notification method that doesn't support it. 304 Notification methods that support :fcc can be discovered at run-time 305 using the mechanism described below (Section 6.1). 307 6.1. Notification-Capability "fcc" 309 This document defines a new notification-capability value "fcc" for 310 use with the notify_method_capability test (see Section 5 of 311 [RFC5435]. For the "fcc" notification-capability, the 312 notify_method_capability test can match one of the following key-list 313 values: 315 yes A copy of the notification message sent using the method 316 identified by the notification-uri can be filed into a target 317 mailbox. 319 no A copy of the notification message sent using the method 320 identified by the notification-uri can not be filed into a target 321 mailbox. 323 Note that the "fcc" notify_method_capability test does not require 324 the notification-uri argument to specify anything other than a 325 scheme. 327 Example: 329 require ["enotify", "fcc"]; 331 if notify_method_capability "xmpp:" "fcc" "yes" { 332 notify :fcc "INBOX.Sent" 333 :message "You got mail" 334 "xmpp:ken@example.com?message;subject=SIEVE"; 335 } else { 336 notify :fcc "INBOX.Sent" 337 :message "You got mail!" 338 "mailto:ken@example.com"; 339 } 341 7. Compatibility with Other Actions 343 The "fcc" extension is not compatible with any Sieve action that does 344 not generate an additional message on behalf of the user. It is an 345 error for a script to use the ":fcc" tagged argument with any such 346 action. 348 Future extensions that define actions that generate additional 349 messages on behalf of the user should describe their compatibility 350 with ":fcc", and how to MIME-encapsulate the message, if required. 352 8. Implementation Status 354 < RFC Editor: before publication please remove this section and the 355 reference to [RFC7942] > 357 This section records the status of known implementations of the 358 protocol defined by this specification at the time of posting of this 359 Internet-Draft, and is based on a proposal described in [RFC7942]. 360 The description of implementations in this section is intended to 361 assist the IETF in its decision processes in progressing drafts to 362 RFCs. Please note that the listing of any individual implementation 363 here does not imply endorsement by the IETF. Furthermore, no effort 364 has been spent to verify the information presented here that was 365 supplied by IETF contributors. This is not intended as, and must not 366 be construed to be, a catalog of available implementations or their 367 features. Readers are advised to note that other implementations may 368 exist. 370 According to [RFC7942], "this will allow reviewers and working groups 371 to assign due consideration to documents that have the benefit of 372 running code, which may serve as evidence of valuable experimentation 373 and feedback that have made the implemented protocols more mature. 374 It is up to the individual working groups to use this information as 375 they see fit". 377 8.1. Cyrus Server 379 The open source Cyrus Server [2] project is a highly scalable 380 enterprise mail system which supports Sieve email filtering at the 381 point of final delivery. This production level Sieve implementation 382 supports all of the requirements described in this document. This 383 implementation is freely distributable under a BSD style license from 384 Computing Services at Carnegie Mellon University [3]. 386 8.2. Oracle Communications Messaging Server 388 The Oracle Communications Messaging Server [4] is a highly scalable, 389 reliable, and available messaging platform. This production level 390 product supports the :fcc extension in conjunction with both the 391 notify and vacation extensions. The implementation meets all the 392 requirements given in this document. The product also supports the 393 imap4flags extension so the :flags may be used in conjunction :fcc. 395 9. Security Considerations 397 The "fcc" extension does not raise any other security considerations 398 that are not already present in [RFC5228], [RFC5230], [RFC5435], and 399 [RFC6131]. 401 10. IANA Considerations 403 10.1. Registration of Sieve Extension 405 To: iana@iana.org 407 Subject: Registration of new Sieve extension 409 Capability name: fcc 411 Description: Adds the ":fcc" parameter to Sieve action commands 412 that generate additional messages. 414 RFC number: RFC XXXX 416 Contact address: The Sieve discussion list 418 10.2. Registration of Notification-Capability Parameter 420 To: iana@iana.org 422 Subject: Registration of a new notification-capability parameter 424 Capability name: fcc 426 Description: Returns whether a copy of the notification message 427 sent using the method identified by the notification-uri parameter 428 to the notify_method_capability test can be filed into a target 429 mailbox. 431 Syntax: Can contain one of two values: "yes" or "no". Values MUST 432 be in lowercase. 434 Permanent and readily available reference(s): This RFC 436 Contact information: The Sieve discussion list 439 11. Acknowledgments 441 The authors would like to thank the following individuals for 442 contributing their ideas and support for writing this specification: 443 Ned Freed, Stan Kalisch, and Alexey Melnikov. 445 12. References 447 12.1. Normative References 449 [I-D.ietf-extra-sieve-special-use] 450 Bosch, S., "Sieve Email Filtering: Delivering to Special- 451 Use Mailboxes", draft-ietf-extra-sieve-special-use-04 452 (work in progress), November 2018. 454 [RFC2045] Freed, N. and N. Borenstein, "Multipurpose Internet Mail 455 Extensions (MIME) Part One: Format of Internet Message 456 Bodies", RFC 2045, DOI 10.17487/RFC2045, November 1996, 457 . 459 [RFC2046] Freed, N. and N. Borenstein, "Multipurpose Internet Mail 460 Extensions (MIME) Part Two: Media Types", RFC 2046, 461 DOI 10.17487/RFC2046, November 1996, 462 . 464 [RFC2047] Moore, K., "MIME (Multipurpose Internet Mail Extensions) 465 Part Three: Message Header Extensions for Non-ASCII Text", 466 RFC 2047, DOI 10.17487/RFC2047, November 1996, 467 . 469 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 470 Requirement Levels", BCP 14, RFC 2119, 471 DOI 10.17487/RFC2119, March 1997, 472 . 474 [RFC2231] Freed, N. and K. Moore, "MIME Parameter Value and Encoded 475 Word Extensions: Character Sets, Languages, and 476 Continuations", RFC 2231, DOI 10.17487/RFC2231, November 477 1997, . 479 [RFC5228] Guenther, P., Ed. and T. Showalter, Ed., "Sieve: An Email 480 Filtering Language", RFC 5228, DOI 10.17487/RFC5228, 481 January 2008, . 483 [RFC5230] Showalter, T. and N. Freed, Ed., "Sieve Email Filtering: 484 Vacation Extension", RFC 5230, DOI 10.17487/RFC5230, 485 January 2008, . 487 [RFC5232] Melnikov, A., "Sieve Email Filtering: Imap4flags 488 Extension", RFC 5232, DOI 10.17487/RFC5232, January 2008, 489 . 491 [RFC5234] Crocker, D., Ed. and P. Overell, "Augmented BNF for Syntax 492 Specifications: ABNF", STD 68, RFC 5234, 493 DOI 10.17487/RFC5234, January 2008, 494 . 496 [RFC5322] Resnick, P., Ed., "Internet Message Format", RFC 5322, 497 DOI 10.17487/RFC5322, October 2008, 498 . 500 [RFC5435] Melnikov, A., Ed., Leiba, B., Ed., Segmuller, W., and T. 501 Martin, "Sieve Email Filtering: Extension for 502 Notifications", RFC 5435, DOI 10.17487/RFC5435, January 503 2009, . 505 [RFC5490] Melnikov, A., "The Sieve Mail-Filtering Language -- 506 Extensions for Checking Mailbox Status and Accessing 507 Mailbox Metadata", RFC 5490, DOI 10.17487/RFC5490, March 508 2009, . 510 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 511 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 512 May 2017, . 514 12.2. Informative References 516 [RFC5436] Leiba, B. and M. Haardt, "Sieve Notification Mechanism: 517 mailto", RFC 5436, DOI 10.17487/RFC5436, January 2009, 518 . 520 [RFC5437] Saint-Andre, P. and A. Melnikov, "Sieve Notification 521 Mechanism: Extensible Messaging and Presence Protocol 522 (XMPP)", RFC 5437, DOI 10.17487/RFC5437, January 2009, 523 . 525 [RFC6131] George, R. and B. Leiba, "Sieve Vacation Extension: 526 "Seconds" Parameter", RFC 6131, DOI 10.17487/RFC6131, July 527 2011, . 529 [RFC7942] Sheffer, Y. and A. Farrel, "Improving Awareness of Running 530 Code: The Implementation Status Section", BCP 205, 531 RFC 7942, DOI 10.17487/RFC7942, July 2016, 532 . 534 12.3. URIs 536 [1] https://tools.ietf.org/html/bcp14 538 [2] http://www.cyrusimap.org/ 540 [3] http://www.cmu.edu/computing/ 542 [4] https://www.oracle.com/industries/communications/enterprise/ 543 products/messaging-server/index.html 545 Appendix A. Change History (To be removed by RFC Editor before 546 publication) 548 Changes since draft-ietf-extra-sieve-fcc-07: 550 o Added comments regarding FCC ABNF per Alexey Melnikov. 552 o Reordered arguments in the "vacation" example to show ":fcc" 553 appearing amongst FCC-OPTS. 555 Changes since draft-ietf-extra-sieve-fcc-06: 557 o Reorganized sections. 559 o Switched to using proper ABNF for FCC and fileinto extensions. 561 o Fcc into INBOX if specified target mailbox doesn't exist. 563 o Editorial changes from Alexey Melnikov. 565 o Other minor editorial changes. 567 Changes since draft-ietf-extra-sieve-fcc-05: 569 o Editorial changes from Jiankang Yao. 571 Changes since draft-ietf-extra-sieve-fcc-04: 573 o Editorial changes from Ned Freed. 575 o Added information on Oracle implementation. 577 Changes since draft-ietf-extra-sieve-fcc-03: 579 o Fixed typo in ABNF. 581 Changes since draft-ietf-extra-sieve-fcc-02: 583 o Updated Keywords boilerplate. 585 o Noted that :fcc mailbox argument and any fileinto extension 586 arguments used wth :fcc have the same syntax and semantics as they 587 have with fileinto. 589 o Removed section on [e]Reject. 591 o Added "fcc" notification-capability. 593 o Added Implementation Status section. 595 o Editorial changes from Ned Freed. 597 Changes since draft-ietf-extra-sieve-fcc-01: 599 o Added text discussing how to handle generated messages that are 600 not in MIME format. 602 o Adjusted ABNF so that tagged arguments that supplement :fcc no 603 longer appear as positional. 605 Changes since draft-ietf-extra-sieve-fcc-00: 607 o Updated abstract with text from Ned. 609 o Added support for :fcc to notify extension. 611 o Prohibit use of :fcc with reject and ereject extensions. 613 o Added registration of the extension with IANA. 615 o Added Acknowledgments. 617 o Minor editorial changes. 619 Authors' Addresses 621 Kenneth Murchison 622 FastMail US LLC 623 1429 Walnut Street - Suite 1201 624 Philadelphia, PA 19102 625 USA 627 Email: murch@fastmailteam.com 629 Bron Gondwana 630 FastMail Pty Ltd 631 Level 2, 114 William Street 632 Melbourne, VIC 3000 633 Australia 635 Email: brong@fastmailteam.com