RFC 2822 on Internet Message Format
RFC Editor <rfc-ed@ISI.EDU> Tue, 24 April 2001 23:48 UTC
Received: from cs.utk.edu ([160.36.56.56]) by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA17990 for <drums-archive@odin.ietf.org>; Tue, 24 Apr 2001 19:48:36 -0400 (EDT)
Received: from localhost (daemon@localhost) by cs.utk.edu with SMTP (cf v2.9s-UTK) id TAA29201; Tue, 24 Apr 2001 19:48:22 -0400 (EDT)
Received: by cs.utk.edu (bulk_mailer v1.13); Tue, 24 Apr 2001 19:48:22 -0400
Received: by cs.utk.edu (cf v2.9s-UTK) id TAA29184; Tue, 24 Apr 2001 19:48:21 -0400 (EDT)
Received: from boreas.isi.edu (marvin@localhost) by cs.utk.edu with ESMTP (cf v2.9s-UTK) id TAA29169; Tue, 24 Apr 2001 19:48:19 -0400 (EDT)
Received: from boreas.isi.edu (128.9.160.161 -> boreas.isi.edu) by cs.utk.edu (smtpshim v1.0); Tue, 24 Apr 2001 19:48:19 -0400
Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by boreas.isi.edu (8.11.2/8.11.2) with ESMTP id f3ONm9529289; Tue, 24 Apr 2001 16:48:09 -0700 (PDT)
Message-Id: <200104242348.f3ONm9529289@boreas.isi.edu>
To: IETF-Announce:;
Subject: RFC 2822 on Internet Message Format
Cc: rfc-ed@ISI.EDU, drums@cs.utk.edu
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Tue, 24 Apr 2001 16:48:09 -0700
From: RFC Editor <rfc-ed@ISI.EDU>
List-Unsubscribe: <mailto:drums-request@cs.utk.edu?Subject=unsubscribe>
A new Request for Comments is now available in online RFC libraries. RFC 2822 Title: Internet Message Format Author(s): P. Resnick, Editor Status: Standards Track Date: March 2001 Mailbox: presnick@qualcomm.com Pages: 50 Characters: 110695 Obsoletes: 822 I-D Tag: draft-ietf-drums-msg-fmt-09.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc2822.txt This standard specifies a syntax for text messages that are sent between computer users, within the framework of "electronic mail" messages. This standard supersedes the one specified in Request For Comments (RFC) 822, "Standard for the Format of ARPA Internet Text Messages", updating it to reflect current practice and incorporating incremental changes that were specified in other RFCs. This document is a product of the Detailed Revision/Update of Message Standards Working Group of the IETF. This is now a Proposed Standard Protocol. This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs.
- RFC 2822 on Internet Message Format RFC Editor