Comments on draft-barber-nntp-imp-05.txt
kherron@campus.mci.net Wed, 10 July 1996 02:54 UTC
Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa07694;
9 Jul 96 22:54 EDT
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa07690;
9 Jul 96 22:54 EDT
Received: from PHEASANT.ACADEM.COM by CNRI.Reston.VA.US id aa00883;
9 Jul 96 22:54 EDT
Received: from academ.com (root@ACADEM.COM [198.137.249.2]) by
pheasant.academ.com (8.7.5/8.6.9) with ESMTP id VAA04924 for
<ietf-nntp@PHEASANT.ACADEM.COM>; Tue, 9 Jul 1996 21:56:25 -0500
Received: from fs.campus.mci.net (fs.campus.mci.net [204.71.74.16]) by
academ.com (8.7.5/8.7.1) with ESMTP id VAA04410 for <ietf-nntp@academ.com>;
Tue, 9 Jul 1996 21:53:18 -0500 (CDT)
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: kherron@campus.mci.net
Received: from girl.campus.mci.net (girl.campus.mci.net [204.71.74.15]) by
fs.campus.mci.net (8.7.5/8.6.12) with ESMTP id TAA07901 for
<ietf-nntp@academ.com>; Tue, 9 Jul 1996 19:52:46 -0700 (PDT)
Received: (from kherron@localhost) by girl.campus.mci.net (8.7.5/8.7.3) id
TAA05821 for ietf-nntp@academ.com; Tue, 9 Jul 1996 19:52:46 -0700 (PDT)
Date: Tue, 9 Jul 1996 19:52:46 -0700 (PDT)
Message-Id: <199607100252.TAA05821@girl.campus.mci.net>
To: ietf-nntp@academ.com
Subject: Comments on draft-barber-nntp-imp-05.txt
X-Sun-Charset: US-ASCII
Comment #1:
RFC 977 says of the ``list command'':
3.6.1. LIST
LIST
Returns a list of valid newsgroups and associated
information. Each newsgroup is sent as a line of text in
the following format:
group last first p
where <group> is the name of the newsgroup, <last> is the
number of the last known article currently in that
newsgroup, <first> is the number of the first article
currently in the newsgroup, and <p> is either 'y' or 'n'
indicating whether posting to this newsgroup is allowed
('y') or prohibited ('n').
No implementation I've ever seen has properly implemented the restriction
on the 4th field. Both INN and the reference implementation just send
whatever is in the active file's 4th field.
Comment #2:
RFC 977 says of the post command:
3.10.1. POST
POST
[...]
If posting is permitted, the article should be presented in the
format specified by RFC850, and should include all required
header lines. After the article's header and body have been
completely sent by the client to the server, a further response
code will be returned to indicate success or failure of the
posting attempt.
[...]
Note that it specifies that the submitted article ``should include all
required header lines.'' In fact, modern implementations only require
From:, Subject:, and Newsgroups: and will happily make up the rest; further,
modern wisdom is for clients to generate as few headers as possible, since
they often do a poor job of it.
- Comments on draft-barber-nntp-imp-05.txt kherron
- Re: Comments on draft-barber-nntp-imp-05.txt Stan Barber