Dismiss
InnovationQ/InnovationQ Plus content will be updated on Sunday, June 25, 10am ET, with new patent and non-patent literature collections. Click here to learn more.
Browse Prior Art Database

Digest message format (RFC1153)

IP.com Disclosure Number: IPCOM000001964D
Original Publication Date: 1990-Apr-01
Included in the Prior Art Database: 2000-Sep-12
Document File: 3 page(s) / 6K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

F.J. Wancho: AUTHOR

Abstract

High traffic volume large mailing lists began to appear on the net in the mid-70s. The moderators of those lists developed a digest message format to enclose several messages into one composite message for redistribution to the mailing list addressees. This format reduces the mailer load in proportion to the number of messages contained within a digest message, and conserves network bandwidth by reducing the size of the headers of the enclosed messages.

This text was extracted from a ASCII Text document.
This is the abbreviated version, containing approximately 51% of the total text.

Network Working Group F. Wancho

Request for Comments: 1153 WSMR

April 1990

Digest Message Format

Status of this Memo

This memo describes the de facto standard Digest Message Format.

This is an elective experimental protocol. Distribution of this memo

is unlimited.

Background

High traffic volume large mailing lists began to appear on the net in

the mid-70s. The moderators of those lists developed a digest

message format to enclose several messages into one composite message

for redistribution to the mailing list addressees. This format

reduces the mailer load in proportion to the number of messages

contained within a digest message, and conserves network bandwidth by

reducing the size of the headers of the enclosed messages.

This RFC documents the digest message format so that others may

follow this format in creating (digestifying) and separating

(undigestifying) digest messages to maintain compatibility with the

programs expecting this de facto standard. Any editorial functions

performed at the discretion of a digest moderator, such as discarding

submissions, editing content to correct spelling and punctuation

errors, inserting comments, and reformatting paragraphs to conform to

width conventions are beyond the scope of this memo.

This memo describes the de facto standard Digest Message Format. It

is not meant to supersede nor replace the generic message

encapsulation format described in RFC 934. It merely documents a

particular message encapsulation format that existed well before RFC

934 was published and continues to be the format of choice for digest

messages.

Description

A digest message is a conventional message consisting of a header and

body conforming to RFC 822 as clarified in RFC 1123. There is no

fixed size. Limitations may exist in intermediate mail gateways

which restrict the size. The typical digest size is 15,000

characters.

The header of a digest message should identify the digest in the

Subject line by listname, the key word, Digest, the volume number

(usually a sequential number either starting at 1 or the last two

digits of the year and incremented by one starting with the first

issue of the next calendar year), and an issue number starting at one

for the first issue of a new calendar year.

The body of a digest message must consist of a Preamble, one or more

enclosed messages, and a Trailer.

The Preamble usually contains a table of contents consisting of the

subject line contents of the enclosed messages, usually indented or

centered, and also may contain brief administrative or other

announcements.

The Preamble must be separated from the remainder of the message by a

line of 70 hyphens followed by a blank line.

Each enclosed message is a conventional message consisting ...