bob@tinman.cis.ohio-state.edu (Bob Sutterfield) (02/22/89)
In article <8902220520.AA00690@photon.stars.flab.fujitsu.junet> umerin@photon.stars.flab.fujitsu.junet (Masanobu UMEDA) writes:
Date: 11 Feb 89 20:41:51 GMT
From: flab!fgw!uunet!pawl.rpi.edu!tale (David C Lawrence)
We have a group here at Rensselaer named rpi.acm.3B2. Trying to
post to this group from GNUS bombs because the group name
somehow comes to be "rpi.acm.3b2".
In fact, GNUS does nothing about the case of newsgroup name... If
the reply says "411 Invalid group name.", that is the problem of
nntpd or something else.
RFC1036 "Standard for Interchange of USENET Messages" says nothing
about the case of the letters in a newsgroup name. However, RFC977
"Network News Transfer Protocol" has a couple of comments.
Section 2.3 (Commands) says: "Commands and command parameters are not
case sensitive. That is, a command or parameter word may be upper
case, lower case, or any mixture of upper and lower case."
Section 3.2.1 (the describing the GROUP command) says: "Note that the
name of the newsgroup is not case-dependent. It must otherwise match
a newsgroup obtained from the LIST command or an error will result."
This would seem to indicate that if a newsgroup already exists on the
server machine with a mixed-case name, then you must specify it in
GROUP the same as it came from LIST. What's the ruling from the
Talmudic scholars of news.software.nntp? Is the existing NNTP
software, or perhaps the existing inews, in violation of the RFCs?