The ''Message-ID'' header
draft-ietf-drums-message-id-00
Document | Type |
Expired Internet-Draft
(drums WG)
Expired & archived
|
|
---|---|---|---|
Author | Jacob Palme | ||
Last updated | 1997-12-03 | ||
RFC stream | Internet Engineering Task Force (IETF) | ||
Intended RFC status | (None) | ||
Formats | |||
Additional resources | Mailing list discussion | ||
Stream | WG state | WG Document | |
Document shepherd | (None) | ||
IESG | IESG state | Expired | |
Consensus boilerplate | Unknown | ||
Telechat date | (None) | ||
Responsible AD | (None) | ||
Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
This is a proposal of a text to include msgfmt in order to clarify the relation between changes in the ''Message-ID'' header and other parts of a message. This information is important, because many mailers use the ''Message-ID'' to eliminate duplicates of the same message, and information may be lost if this is not done the right way. Temporary note This document does not at this time (21 November 1997) represent any consensus opinion in the drums working group.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)