Re: [Technical Errata Reported] RFC5537 (1993)
Russ Allbery <[email protected]> Mon, 28 Dec 2009 12:31:21 -0800
| Newsgroups | gmane.ietf.usenet.format |
|---|---|
| Organization | The Eyrie |
| Message-ID | <[email protected]> |
RFC Errata System <[email protected]> writes: > Type: Technical > Reported by: Julien =C3=89lie <[email protected]> > Section: 5.2.1.1 > Original Text > ------------- > A newgroup control message requesting creation of the moderated > newsgroup example.admin.info. > From: "example.* Administrator" <[email protected]> > Newsgroups: example.admin.info > Date: 27 Feb 2002 12:50:22 +0200 > Subject: cmsg newgroup example.admin.info moderated > Approved: [email protected] > Control: newgroup example.admin.info moderated > Message-ID: <[email protected]> > MIME-Version: 1.0 > Content-Type: multipart/mixed; boundary=3D"nxtprt" > Content-Transfer-Encoding: 8bit > Corrected Text > -------------- > A newgroup control message requesting creation of the moderated > newsgroup example.admin.info. > | Path: not-for-mail > From: "example.* Administrator" <[email protected]> > Newsgroups: example.admin.info > Date: 27 Feb 2002 12:50:22 +0200 > Subject: cmsg newgroup example.admin.info moderated > Approved: [email protected] > Control: newgroup example.admin.info moderated > Message-ID: <[email protected]> > MIME-Version: 1.0 > Content-Type: multipart/mixed; boundary=3D"nxtprt" > Content-Transfer-Encoding: 8bit > Notes > ----- > As the mandatory Path: header field is missing, this control message is > only a proto-article. > A control message is defined in Section 5 as an article which contains a > Control: header field. Therefore, a Path: header field should be added > to the headers of this sample newgroup control article. This change is correct. Thanks! --=20 Russ Allbery ([email protected]) <http://www.eyrie.org/~eagle/>