As per Relevance of the word starting, we have this rfc below:
Network Working Group F.
Request for Comments: 1153
April 1990
Digest Message
Status of this
This memo describes the de facto standard Digest Message Format
This is an elective experimental protocol. Distribution of this
is unlimited
High traffic volume large mailing lists began to appear on the net
the mid-70s. The moderators of those lists developed a
message format to enclose several messages into one composite
for redistribution to the mailing list addressees. This
reduces the mailer load in proportion to the number of
contained within a digest message, and conserves network bandwidth
reducing the size of the headers of the enclosed messages
This RFC documents the digest message format so that others
follow this format in creating (digestifying) and
(undigestifying) digest messages to maintain compatibility with
programs expecting this de facto standard. Any editorial
performed at the discretion of a digest moderator, such as
submissions, editing content to correct spelling and
errors, inserting comments, and reformatting paragraphs to conform
width conventions are beyond the scope of this memo
This memo describes the de facto standard Digest Message Format.
is not meant to supersede nor replace the generic
encapsulation format described in RFC 934. It merely documents
particular message encapsulation format that existed well before
934 was published and continues to be the format of choice for
messages
A digest message is a conventional message consisting of a header
body conforming to RFC 822 as clarified in RFC 1123. There is
fixed size. Limitations may exist in intermediate mail
which restrict the size. The typical digest size is 15,000
characters
The header of a digest message should identify the digest in
Wancho [Page 1]
RFC 1153 Digest Message Format April 1990
Subject line by listname, the key word, Digest, the volume
(usually a sequential number either starting at 1 or the last
digits of the year and incremented by one starting with the
issue of the next calendar year), and an issue number starting at
for the first issue of a new calendar year
The body of a digest message must consist of a Preamble, one or
enclosed messages, and a Trailer
The Preamble usually contains a table of contents consisting of
subject line contents of the enclosed messages, usually indented
centered, and also may contain brief administrative or
announcements
The Preamble must be separated from the remainder of the message by
line of 70 hyphens followed by a blank line
Each enclosed message is a conventional message consisting of
header and body, separated by a blank line. If they exist in
original message header, the following lines must be retained as-
in the reconstructed header: Date:, From:, To:, Cc:, Subject:,
Message-ID:, and Keywords:, rearranged to appear in that order
Retaining the Summary: line is optional. Lines include
lines as defined in the RFCs. All other header lines should
discarded, especially Received lines. All leading and trailing
lines should be removed from the message body. The message body
be scanned to replace with a blank the first character of any
of exactly and only 30 hyphens
Each enclosed message must be separated from the the remainder of
digest message by a blank line before and after a line of 30 hyphens
The Trailer immediately follows the blank line of message
following the last enclosed message. The Trailer consists of
lines. The first line must begin with the words, End of, followed
the listname a blank and the word Digest which is usually followed
volume and issue number on the same line. The second and last
of the Trailer and the entire message is a line of asterisks
to underline the line immediately above it
The following example serves as a template for a digest
conforming to this memo. It contains a header, and a body
of a Preamble, two enclosed messages, and a Trailer. fqhn
Fully Qualified Host Name. The Date: lines are examples only
Wancho [Page 2]
RFC 1153 Digest Message Format April 1990
Date: ddd, dd mmm yy hh:mm:ss
From: listname-REQUEST@
Reply-To: listname@
Subject: listname Digest Vyy #
To: listname@
listname Digest ddd, dd mmm yy Volume yy : Issue
Today's Topics
Message One
Message Two
Administrivia
Messages from the list moderator or maintainer go here
----------------------------------------------------------------------
Date: ddd, dd mmm yy hh:mm:ss
From: Joe User <username@fqhn
Subject: Message One
This is the message body of the first message
------------------------------
Date: ddd, dd mmm yy hh:mm:ss
From: Jane User <username@fqhn
Subject: Message Two
This is the body of message two
------------------------------
End of listname Digest Vyy Issue #
************************************
Wancho [Page 3]
RFC 1153 Digest Message Format April 1990
Security
Security issues are not discussed in this memo
Author's
Frank J.
USAISC-White
ASQNC-TWS-SS-C (F. Wancho, Building 1512)
White Sands Missile Range, NM 88002-5506
Phone: (505) 678-3009
Email: WANCHO@WSMR-SIMTEL20.ARMY.
Wancho [Page 4]
if you see any problems within the linking, don't worry be happy,
this is version 0.1 of the Relevance System and you gotta expect some crappy subroutines sometimes,
just be content we did not write this in Java, which would have made this "bigger and better" HAHAHHA.
RFC documents can be found at I.E.T.F.
Relevance System Copyright © 2002 Spectrum WorldResearch
other technical nosh by ServerMasters Corporation
collaboration of BobX
