Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!shadooby!ginosko!uunet!munnari.oz.au!csc!gih900
From: gih900@csc.anu.oz (Geoff Huston)
Newsgroups: news.software.anu-news
Subject: Re: NEWS v5.9 nntp_server
Message-ID: <792.2535a5e1@csc.anu.oz>
Date: 13 Oct 89 09:07:44 GMT
References: <10.253106ce@csc.fi>
Organization: Computer Services, Australian National University
Lines: 41

In article <10.253106ce@csc.fi>, netmgr@csc.fi (Pekka Kytolaakso) writes:
> 
> I'm using nn (NoNews if Good News) as an agent to read news on a Sun
> workstation. The POST command of the server seem's to have changed.
> It now REQUIRES message-id, date and path headers that mini-inews, that comes
> with nntp.1.5 dosnt supply, and this causes POST/Followup to fail.

The NNTP RFC is VERY unclear about the responsibilities of the server and the
client in the format of the POST article contents... I was originally simply
treating a POST as a similar transaction to the IHAVE action, and the article
text was simply batched for later processing by the server. I then changed the
POST command to perform a similar action to the local POST command - i.e. parse
the header, check out that the required headers are present, etc.

This is all fixable. Can someone (Pekka?) provide me with a "typical" article
that the client will attempt to send following a POST command?

> There also is some trouble with the access check. I have nntp_access.news (or
> whatecr it was) that allows everyone to read/post/transfer to/from any
> newsgroup. When I try mini-inews with a file that has the needed headerfields
> added the tranfser end in 'News not posted/posting to newsgroup no allowed'.
> Is there some other accesscheck than the accessfile? I'll try to debug
> the server to see what the problem is and will report if i find something
> wrong.

Yes - in so far as the server now uses the remote client's username and node
name to perform local access checks on locally restricted newsgroups in
repsonse to the POST command.

Geoff Huston

> PS Some time ago there was a dicsussion about how to make shure only one
>    add or skim is running at a time. It took us 3 months but we finally 
>    figured an easy (an foolproof) way to do it. We gave news an own batch 
>    queue with joblimit=1.
I do it with

	$ SET ON
	$ ON ERROR THEN GOTO ABORT
	$ SET PROCESS/NAME="NEWS-ADD"
           etc