Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!wuarchive!kuhub.cc.ukans.edu!anu-news!list From: munnari!csc.anu.oz.au!gih900@UUNET.UU.NET (Geoff Huston) Newsgroups: news.software.anu-news Subject: RE: Old hack or new administrator? Message-ID: <8909172232.AA23411@uunet.uu.net> Date: 18 Sep 89 13:21:23 GMT Sender: ANU-NEWS Discussion Reply-To: Geoff Huston Lines: 33 X-cc: GIH900@uunet.UU.NET Tom Limoncelli writes:... >Question #1: > >I do have two of our VAXes exchanging news, so it shouldn't be too >hard to get on Usenet, and we have VMS UUCP, but do all the messages >arrive as mail to USENET or is it more complicated than that? The RFC on NEWS (1036) indicates a number of ways of transferring NEWS between USENET sites. In respect to mail there are intended to be two addresses: If the feed site mails individual news items to the receiving site then the feed site should mail to the address "inews" on the receiving site. If the news is batched (using #! rnews delimiters) then the sender should mail to the address "rnews" on the receiver's site. >Question #2: > >Also, right now, if someone posts to CONTROL or JUNK there isn't >anything to stop them. Should I make these /RESTRICTED and only have >NEWSMGR be on the member's list? It doesn't matter whether local users post to "junk" or "control" newsgroups - you should set up the NEWS.SYS file so that these messages go nowhere (or, as you suggest, set them RESTRICTED). The mechanism to launch control messages into the USENET is the ability to insert a "Control:" header into the newsitem. As this point there are only two ways to do this within NEWS: the CANCEL command generates a "Control: cancel" message, (which only the original poster, the local supervisor, or the local news manager may generate) or the command "POST/Control="string"" which is restricted to the local news manager. cheers, Geoff Huston gih900@csc.anu.oz.au