Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!mips!apple!bbn.com!papaya.bbn.com!rsalz
From: rsalz@bbn.com (Rich Salz)
Newsgroups: news.software.b
Subject: Re: LET'S NAME THE GUILTY POSTING SOFTWARE!!!
Message-ID: <3637@litchi.bbn.com>
Date: 23 Jun 91 02:13:56 GMT
References: <6068@gazette.bcm.tmc.edu> <1991Jun19.154645.11885@zoo.toronto.edu> <1991Jun19.172544.32267@mp.cs.niu.edu> <6098@gazette.bcm.tmc.edu>
Organization: BBN Systems and Technology, Inc.
Lines: 18

In <6098@gazette.bcm.tmc.edu> sob@tmc.edu (Stan Barber) writes:
>Mini-inews is NOT a transport. It is just a feed into NNTP which in turn
>feeds it into the REAL inews in the news transport. THAT is where all these
>checks should occur.
I disagree.  I think that a program that took a user's article, verified
all the headers, processed the .signature, and then fed it to the NNTP
port of the campus server would be a very useful thing indeed.  I wrote
one, it's in beta-test right now.  For historical compatibility, I
call the program inews.  If my inews accepts your article, you can be
very sure that the only reason the server would reject it is because of
a transient failure like disk full.

It's a very simple program to write:
    litchi% wc -l frontends/inews.c
	 937    frontends/inews.c
-- 
Please send comp.sources.unix-related mail to rsalz@uunet.uu.net.
Use a domain-based address or give alternate paths, or you may lose out.