idnits 2.17.1 draft-ietf-mailext-mail-attributes-00.txt: ** The Abstract section seems to be numbered Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Cannot find the required boilerplate sections (Copyright, IPR, etc.) in this document. Expected boilerplate is as follows today (2024-04-19) according to https://trustee.ietf.org/license-info : IETF Trust Legal Provisions of 28-dec-2009, Section 6.a: This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 2: Copyright (c) 2024 IETF Trust and the persons identified as the document authors. All rights reserved. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 3: This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. 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. ** The document seems to lack a 1id_guidelines paragraph about Internet-Drafts being working documents. ** The document seems to lack a 1id_guidelines paragraph about 6 months document validity -- however, there's a paragraph with a matching beginning. Boilerplate error? ** The document seems to lack a 1id_guidelines paragraph about the list of current Internet-Drafts. ** The document seems to lack a 1id_guidelines paragraph about the list of Shadow Directories. == The page length should not exceed 58 lines per page, but there was 13 longer pages, the longest (page 1) being 59 lines Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an Abstract section. (A line matching the expected section header was found, but with an unexpected indentation: ' 2. Abstract' ) ** The document seems to lack an Introduction section. ** The document seems to lack a Security Considerations section. ** 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.) Miscellaneous warnings: ---------------------------------------------------------------------------- == Line 108 has weird spacing: '...te name docu...' == Line 132 has weird spacing: '...te name docu...' == Line 152 has weird spacing: '...te name docu...' == Line 213 has weird spacing: '...te name docu...' == Line 258 has weird spacing: '...te name docu...' == (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 (September 1995) is 10444 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- -- Missing reference section? '1' on line 511 looks like a reference -- Missing reference section? '2' on line 514 looks like a reference -- Missing reference section? '3' on line 517 looks like a reference -- Missing reference section? '4' on line 520 looks like a reference -- Missing reference section? '5' on line 523 looks like a reference -- Missing reference section? '6' on line 527 looks like a reference -- Missing reference section? '7' on line 532 looks like a reference Summary: 11 errors (**), 0 flaws (~~), 7 warnings (==), 9 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Network Working Group J. Palme 2 Internet Draft Stockholm University/KTH 3 Sweden 4 Category: Informational March 1995 5 Expires September 1995 7 Common Internet Message Attributes 9 1. Status of this Memo 11 This document is an Internet-Draft. Internet-Drafts are working 12 documents of the Internet Engineering Task Force (IETF), its 13 areas, and its working groups. Note that other groups may also 14 distribute working documents as Internet-Drafts. 16 Internet-Drafts are draft documents valid for a maximum of six 17 months and may be updated, replaced, or obsoleted by other 18 documents at any time. It is inappropriate to use Internet- 19 Drafts as reference material or to cite them other than as 20 ``work in progress.'' 22 To learn the current status of any Internet-Draft, please check 23 the ``1id-abstracts.txt'' listing contained in the Internet- 24 Drafts Shadow Directories on ftp.is.co.za (Africa), 25 nic.nordu.net (Europe), munnari.oz.au (Pacific Rim), 26 ds.internic.net (US East Coast), or ftp.isi.edu (US West Coast). 28 This memo provides information for the Internet community. This 29 memo does not specify an Internet standard of any kind, since 30 this document is mainly a compilation of information taken from 31 other RFC-s.. Distribution of this memo is unlimited. 33 2. Abstract 35 This memo contains a table of commonly occurring attributes in 36 headings and on envelopes of e-mail messages. The document compiles 37 information from other RFC-s such as RFC 821, RFC 822, RFC 1036, 38 RFC 1327, RFC 1496, RFC 1521 and X.400. A few commonly occurring 39 attributes which are not defined in RFC-s are also included. For 40 each attribute, the memo gives a short description and a reference 41 to the RFC or X.400 part, in which the attribute is defined. 43 3. Table of contents 45 4. Introduction 46 5. Use of gatewaying attributes 47 6. Table of attributes 48 6.1 Addressing information 49 6.2 Envelope and format information 50 6.3 Header fields containing mailbox names and addressable entities 51 6.4 Message identification and referral attributes 52 6.5 Other textual attributes 53 6.6 Attributes containing dates and times 54 6.7 Attributes containing other types of information 55 6.8 Resent-attributes 56 6.9 Sometimes occurring heading fields in Internet mail 57 which are not according to standard 58 7. Acknowledgments 59 8. References 60 9. Author's address 61 Appendix A: Attributes sorted by Internet RFC document in which 62 they appear 64 4. Introduction 66 Many different Internet standards and RFC-s define attributes which 67 may occur on Internet Mail Messages and Network News Articles. The 68 intention of this document is to list all such attributes in one 69 document as an aid to people developing message systems or interested 70 in Internet Mail standards. 72 The document contains all heading attributes which the author has 73 found in the following Internet standards: RFC 821 [1], RFC 822 [2], 74 RFC 1036 [3], RFC 1327 [4], RFC 1496 [5] and RFC 1521 [6]. Note in 75 particular that heading attributes defined in RFC 1421-1424, Privacy 76 Enhancement for Internet Electronic Mail, are not included. A few 77 additional attributes which often can be found in e-mail headings 78 are also included. 80 For each heading attribute, the document gives a short description and 81 a reference to the Internet standard or RFC, in which they are defined. 82 Information about corresponding attributes in X.400 is also given 83 when available. 85 5. Use of gatewaying attributes 87 RFC 1327 defines a number of new attributes in Internet mail, which 88 are defined to map attributes which X.400 have but which were 89 previously not standardized in Internet mail. Some of these attributes 90 are obviously useful also as stand-alone Internet mail message 91 attributes. The fact that an attribute occurs in RFC 1327 indicates 92 that it is recommended for use in gatewaying messages between X.400 93 and Internet mail, but does not necessarily mean that the attribute 94 is recommended for messages wholly within Internet mail. However, some 95 of these attributes may eventually get accepted also for usage within 96 Internet mail. 98 Fields are given here in the spelling used in e-mail headers. This 99 may sometimes be English, sometimes American spelling. One attribute, 100 "Organisation/Organization" occurs in e-mail headers sometimes with 101 English, sometimes with American spelling. 103 6. Table of attributes 105 6.1 Addressing information 107 Description Internet att- Internet X.400 X400 108 ribute name document attribute document 109 -----------------------+-------------+------------+------------+-------+ 111 Original sender. Should MAIL FROM RFC 821 Originator X.411 112 in Internet be empty name 113 when sending 114 notifications, and be 115 the list administrator 116 when forwarding from a 117 distribution list. 119 Relative address to the Return-Path: RFC 821 Trace X.411 120 original sender along 121 the reverse path 122 through which the 123 message was sent 125 Recipient to which RCPT TO RFC 821 Recipient X.411 126 message is to be name 127 delivered. 129 6.2 Envelope and format information 131 Description Internet att- Internet X.400 X400 132 ribute name document attribute document 133 -----------------------+-------------+------------+------------+-------+ 135 All that is inside the DATA RFC 821 Content X.411 136 envelope. 138 Trace of MTA-s which a Received: RFC 822: Trace X.411 139 message has passed. 4.3.2 141 MIME protocol version MIME-Version: RFC 1521: 3 Mapped into RFC 142 body part 1496 144 Format of content Content-Type: RFC 1521: 4 Mapped into RFC 145 (character set etc.) body part 1496 147 Coding method used in Content- RFC 1521: 5 148 content. Transfer- 149 Encoding 151 Description Internet att- Internet X.400 X400 152 ribute name document attribute document 153 -----------------------+-------------+------------+------------+-------+ 155 List of MTA-s passed. Path: RFC 1036: Trace X.411 156 2.1.6 158 Special Usenet News Control: RFC 1036: 159 actions. 2.2.6 161 Trace of distribution DL-Expansion- RFC 1327 DL Expansion X.411 162 lists passed. history- History 163 indication indication 165 Which body part types Original- RFC 1327 Original- X.411 166 occur in this message. Encoded- encoded- 167 Information- information- 168 Types: types 170 Special informational Message-Type: RFC 1327 Notification X.411 171 message. Delivery Report 173 Controls whether this Alternate- RFC 1327 Alternate- X.411 174 message may be recipient: recipient- 175 forwarded to a allowed 176 postmaster if delivery 177 is not possible to the 178 intended recipient. 179 Default: Allowed. 181 Whether non-delivery Prevent- RFC 1327 Originator X.411 182 report is wanted at NonDelivery- ReportRequest 183 delivery error. Default Report: 184 is to want such a 185 report. 187 Whether a delivery Generate- RFC 1327 Originator X.411 188 report is wanted at Delivery- ReportRequest 189 successful delivery. Report: 190 Default is not to 191 generate such a report. 193 Whether recipients are Disclose- RFC 1327 Disclosure- X.411 194 to be told the names of Recipients: of-recipients 195 other recipients of the 196 same message. This is 197 primarily an X.400 198 facility, such 199 disclosure is in 200 Internet mail done via 201 the To:, Cc: and Bcc: 202 heading fields. 204 Indicates whether the Content- RFC 1327 Content-return- X.411 205 content of a message is Return request 206 to be returned with 207 non-delivery 208 notifications. 210 6.3 Header fields containing mailbox names and addressable entitities 212 Description Internet att- Internet X.400 X400 213 ribute name document attribute document 214 -----------------------+-------------+------------+------------+-------+ 216 Replacement for "From:" Reply-To: RFC 822: Reply- X.420 217 to which replies are to 4.4.3 recipients 218 be sent. 220 Author, approver. From: RFC 822: Authorizing- X.420 221 4.4.1 users 223 Moderator. Approved: RFC 1036: Authorizing- X.420 224 2.2.11 users 226 Sender information Sender: RFC 822: Originator X.420 227 inside the envelope. 4.4.2 229 Main recipients. To: RFC 822: Primary- X.420 230 4.5.1 recipients 232 Additional recipients. Cc: RFC 822: Copy- X.420 233 4.5.2 recipients 235 Recipients not shown to Bcc: RFC 822: Blind-copy- X.420 236 other recipients. 4.5.3 recipients 238 In Usenet News: group Newsgroups: RFC 1036: Primary- X.420 239 to which this article 2.1.3 Recipient 240 was posted. In e-mail: 241 either group to which 242 this message was posted 243 or group to which the 244 article this message is 245 a reply-to was posted. 247 Where group replies to Followup-To: RFC 1036: 248 this message are to be 2.2.3 249 sent. 251 Limitation on where Distribution: RFC 1036: 252 this message can be 2.2.7 253 distributed. 255 6.4 Message identification and referral attributes 257 Description Internet att- Internet X.400 X400 258 ribute name document attribute document 259 -----------------------+-------------+------------+------------+-------+ 261 Unique ID of this Message-ID: RFC 822: IPM X.420 262 message. 4.6.1 Identifier 264 Unique ID of one body Content-ID: RFC 1521: not 265 part of the content of 6.1 available 266 a message. 268 Reference to message In-Reply-To: RFC 822: Replied-to- X.420 269 which this message is a 4.6.2 IPM 270 reply to. 272 Reference to other References: RFC 822: Related-IPMs X.420 273 related messages. 4.6.3 275 Reference to previous Obsoletes: RFC 1327 Obsoleting X.420 276 message being corrected 277 and replaced. 279 6.5 Other textual attributes 281 Description Internet att- Internet X.400 X400 282 ribute name document attribute document 283 -----------------------+-------------+------------+------------+-------+ 285 Search keys for data Keywords: RFC 822: Heading RFC 1327 286 base retrieval. 4.6.4 extension 288 Title, heading, Subject: RFC 822: Subject X.420 289 subject. 4.7.1 291 Comments on a message. Comments: RFC 822: Extra body X.420 292 4.7.2 part 294 Description of a Content- RFC 1521: Heading RFC 1327 295 particular body part description: 6.2 extension 296 of a message. 298 Organisation to which Organization: RFC 1036: organization- X.520 299 the sender of this 2.2.8 name 300 message belongs. 302 Short text describing Summary: RFC 1036: Heading RFC 1327 303 a longer message. 2.2.10 extension??? 305 A text string which Content- RFC 1327 Content- X.411 306 identifies the content identifier: identifier 307 of a message. 309 6.6 Attributes containing dates and times 311 Description Internet att- Internet X.400 X400 312 ribute name document attribute document 313 -----------------------+-------------+------------+------------+-------+ 315 The time when a Delivery- RFC 1327 Message- X.411 316 message was delivered Date: delivery 317 to its recipient. time 319 In Internet, the date Date: RFC 822: Message- X.411 320 when a message was 5.1 submission- 321 written, in X.400, the time 322 time a message was 323 submitted. 325 A suggested expiration Expires: RFC 1036: Expiry Date X.420 326 date. Can be used both 2.2.4 Indication 327 to limit the time of an 328 article which is not 329 meaningful after a 330 certain date, and to 331 extend the storage of 332 important articles. 334 Time at which a message Expiry-Date: RFC 1327 Expiry Date X.420 335 loses its validity. Indication 337 Latest time at which a Reply-By: RFC 1327 ReplyTime X.420 338 reply is requested (not Field 339 demanded). 341 6.7 Attributes containing other types of information 343 Description Internet att- Internet X.400 X400 344 ribute name document attribute document 345 -----------------------+-------------+------------+------------+-------+ 347 Can be normal, urgent Priority: RFC 1327 Priority X.411 348 or non-urgent and can 349 influence transmission 350 speed and delivery. 352 Size of the message. Lines: RFC 1036: Heading RFC 1327 353 2.2.12 extension??? 355 Has been automatically Auto- RFC 1327 Auto- X.420 356 forwarded. Forwarded: Forwarded 357 Indication 359 Can be high, normal or Importance: RFC 1327 Importance X.420 360 low and is only used in 361 the recipient client 362 (UA). 364 Description Internet att- Internet X.400 X400 365 ribute name document attribute document 366 -----------------------+-------------+------------+------------+-------+ 368 Body parts are missing. Incomplete- RFC 1327 Incomplete X.420 369 Copy: Copy 371 Can include a two- Language: RFC 1327 Language X.420 372 character code for the 373 natural language used 374 in a message, e.g. "en" 375 for English. 377 Can be personal, Sensitivity: RFC 1327 Sensitivity X.420 378 private, company- 379 confidential or 380 absent. 382 The body of this mess- Conversion: RFC 1327 Implicit- X.411 383 age may not be conver- conversion- 384 ted from one charac- prohibited 385 ter set to another. 387 The body of this Conversion- RFC 1327 Conversion- X.411 388 message may not be With-Loss: with-loss- 389 converted from one prohibited 390 character set to 391 another if information 392 will be lost. 394 Can be used in Internet Discarded- RFC 1327 Extensions X.420 395 mail to indicate X.400 X400-IPMS- Field 396 extensions which Extensions: 397 could not be mapped 398 to Internet mail Discarded- RFC 1327 Extensions X.420 399 format. X400-MTS- Field 400 Extensions: 402 6.8 Resent-attributes 404 Description Internet att- Internet X.400 X400 405 ribute name document attribute document 406 -----------------------+-------------+------------+------------+-------+ 408 When forwarding a Resent-Reply- RFC 822, Embedded X.420 409 message, attributes To:, Resent- C.3.3 message 410 referring to the From:, Resent- bodies 411 forwarding, not to the Sender:, should be 412 original message. Resent-From:, used for 413 Resent-Date:, forwarding. 414 Note: MIME specifies Resent-To:, 415 another way of resen- Resent-cc:, 416 ding messages, using Resent-bcc:, 417 the "Message" Content- Resent- 418 Type. Message-ID: 420 6.9 Sometimes occurring heading fields in Internet mail 421 which are not according to standard 423 This chapter does not include a complete collection of all heading 424 attributes, such a list would be much longer. It contains a few 425 attributes which occur frequently and for which an explanation may be 426 useful here. 428 Description Internet att- Internet X.400 X400 429 ribute name document attribute document 430 -----------------------+-------------+------------+------------+-------+ 432 Inserted by Sendmail Apparently- RFC 1211 433 in certain cases, lis- to: 434 ting recipients deriv- 435 ed from the envelope 436 into the message 437 heading. This behavi- 438 or is not quite pro- 439 per, MTA-s should not 440 modify headings (ex- 441 cept inserting Reci- 442 eved lines), and it 443 can in some cases 444 cause Bcc recipients 445 to be wrongly divulged. 447 Inserted by certain Content- 448 mailers to indicate length: 449 the size in bytes of 450 the message text. Can 451 cause several robust- 452 ness and interoperabi- 453 lity problems and is 454 not recommended. 456 Pre-MIME way of indi- Encoding: RFC 1154 457 cating encoding format 458 in message. 460 Address to which Errors-To:, 461 notifications are to Return- 462 be sent. Internet Receipt-To: 463 standards recommend, 464 however, the use of 465 RCPT TO and Return- 466 Path, not Errors-To, 467 for this. 469 Fax number of the Fax:, X.520 470 originator. Telefax: 472 Description Internet att- Internet X.400 X400 473 ribute name document attribute document 474 -----------------------+-------------+------------+------------+-------+ 476 Name of file in which a Fcc: 477 copy of this message is 478 stored. 480 Information about the Mail-System- 481 client software of the Version:, 482 originator. Mailer: 484 See Organization. Organisation: organization X.520 485 -name 486 Information about the Originating- 487 client software of the Client: 488 originator. 490 Phone number of the Phone: O/R X.420 491 originator. Descriptor, X.520?? 492 telephone- 493 number 495 Used in Usenet News Supersedes: 496 in similar ways to 497 the "Obsoletes" attri- 498 bute described earlier 499 in this document. 501 7. Acknowledgments 503 Harald Tveit Alvestrand and several other people has helped me with 504 compiling this list. I alone take responsibility for any errors which 505 may be in the list. 507 An earlier version of this list has been published as part of [7]. 509 8. References 511 [1] J. Postel: "Simple Mail Transfer Protocol", STD 10, RFC 821, 512 August 1982. 514 [2] D. Crocker: "Standard for the format of ARPA Internet text 515 messages." STD 11, RFC 822, August 1982. 517 [3] M.R. Horton, R. Adams: "Standard for interchange of USENET 518 messages", RFC 1036, December 1987. 520 [4] S. Hardcastle-Kille: "Mapping between X.400(1988) / ISO 10021 521 and RFC 822", RFC 1327 May 1992. 523 [5] H. Alvestrand & J. Romaguera: "Rules for Downgrading Messages 524 from X.400/88 to X.400/84 When MIME Content-Types are Present 525 in the Messages", RFC 1496, August 1993. 527 [6] 1521 N. Borenstein & N. Freed: "MIME (Multipurpose Internet 528 Mail Extensions) Part One: Mechanisms for Specifying and 529 Describing the Format of Internet Message Bodies", 530 RFC 1521, September 1993. 532 [7] J. Palme: "Electronic Mail", Artech House publishers, London- 533 Boston January 1995. 535 9. Author's address 537 Jacob Palme Phone: +46-8-16 16 67 538 Stockholm University/KTH Fax: +46-8-703 90 25 (not fast) 539 Electrum 230 E-mail: jpalme@dsv.su.se 540 S-164 40 Kista, Sweden 542 Appendix A: 543 Attributes sorted by Internet RFC document in which they appear. 545 RFC 821 546 ------- 548 DATA 549 MAIL FROM 550 RCPT TO 552 RFC 822 553 ------- 555 Bcc 556 Cc 557 Comments 558 Date 559 From 560 In-Reply-To 561 Keywords 562 Message-ID 563 Received 564 References 565 Reply-To 566 Resent- 567 Resent-bcc 568 Resent-Date 569 Resent-From 570 Resent-From 571 Resent-Message-ID 572 Resent-Reply-To 573 Resent-ToResent-cc 574 Return-Path 575 Sender 576 Sender 577 Subject 578 To 579 RFC 1036 580 -------- 582 Approved 583 Control 584 Distribution 585 Expires 586 Followup-To 587 Lines 588 Newsgroups 589 Organization 590 Path 591 Summary 593 RFC 1327 594 -------- 596 Alternate-recipient 597 Auto-Forwarded 598 Autoforwarded 599 Content-identifier 600 Content-Return 601 Conversion 602 Delivery-Date 603 Discarded-X400-IPMS-Extensions 604 Discarded-X400-MTS-Extensions 605 Disclose-Recipients 606 DL-Expansion-History 607 Donversion-With-Loss 608 Expiry-Date 609 Generate-Delivery-Report 610 Importance 611 Incomplete-Copy 612 Language 613 Message-Type Delivery 614 Obsoletes 615 Original-Encoded-Information-Types 616 Prevent-NonDelivery-Report 617 Priority 618 Reply-By 619 Report 620 Sensitivity 622 RFC 1521 623 -------- 625 Content-description 626 Content-ID 627 Content-Transfer-Encoding 628 Content-Type 629 MIME-Version 630 Not Internet standard 631 --------------------- 633 Apparently-to 634 Content-length 635 Encoding 636 Errors-To 637 Fax 638 Fcc 639 Mail-System-Version 640 Mailer 641 Organisation 642 Originating-Client 643 Phone 644 Return-Receipt-To 645 Supersedes 646 Telefax