Xref: utzoo news.software.b:6401 news.newusers.questions:3488 news.software.nntp:980
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!samsung!uunet!zephyr.ens.tek.com!uw-beaver!cornell!rochester!kodak!ispd-newsserver!dcox
From: dcox@tweety.ssd.kodak.com (Don Cox (253-7121))
Newsgroups: news.software.b,news.newusers.questions,news.software.nntp
Subject: nntp_access file
Message-ID: <1990Dec14.175337.6145@ssd.kodak.com>
Date: 14 Dec 90 17:53:37 GMT
Sender: news@ssd.kodak.com
Distribution: na
Organization: Eastman Kodak
Lines: 22
Originator: dcox@tweety.ssd.kodak.com

Forgive me for being thick as a brick, but I can't grasp the meaning
of the second field in the nntp_access file.  The third field is
easy enough to understand ... a 'post' means the machine can post 
articles on that news server, a 'no' means that it can't.  But
the read/xfer/both/no has me somewhat confused.

According to the man pages on nntpd, it controls the read permission.
What are they talking about when, if the entry is 'read', all commands
but IHAVE and POST can be executed?  Same for 'xfer' ... "matching hosts 
can only  execute commands  used  for transferring news, such as NEWNEWS, 
NEWGROUPS, IHAVE, and ARTICLE with message-id  parameters."  Then
'both' goes on to say that the host can execute all commands but POST.

It sounds like the second field is controlling whether a host can post
articles or not; does it over-ride the third field, or what?

Thanks.
-- 
                  Don Cox
Phone (716) 253-7121      KMX (716) 253-7998
INTERNET    dcox@ssd.kodak.com
When an eel bites your leg, and the pain makes you beg, that's a moray!