Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!bcm!tmc.edu!sob
From: sob@tmc.edu (Stan Barber)
Newsgroups: news.software.b
Subject: Re: LET'S NAME THE GUILTY POSTING SOFTWARE!!!
Message-ID: <6102@gazette.bcm.tmc.edu>
Date: 20 Jun 91 13:39:17 GMT
References: <1991Jun19.172544.32267@mp.cs.niu.edu> <6098@gazette.bcm.tmc.edu> <1991Jun20.114358.4871@mp.cs.niu.edu>
Sender: usenet@bcm.tmc.edu
Organization: Baylor College of Medicine, Houston, TX
Lines: 25
Nntp-Posting-Host: tmc.edu

In article <1991Jun20.114358.4871@mp.cs.niu.edu> rickert@mp.cs.niu.edu (Neil Rickert) writes:
>It also does not support all of the options newsreaders use in a REAL inews,
>and it sometimes takes interminably long to complete when there is a human
>sitting impatiently waiting to proceed with the next order of business. 
>Both of these facts encourage installation of buggy shell script front ends to>inews which further contribute to the real problem.

Let's see if we can agree on the REAL problem.
The REAL problem as I see it is that the inews in the news transport does
not to an adequate job of checking headers and returning bad articles to the
user. 

Now, we could add some smarts to mini-inews to move the detection closer to
the user. How does this fix the REAL problem?

What about software that DOES NOT USE mini-inews to post articles?

I don't disagree with the idea of adding capabilities to mini-inews to 
support all the optional flags of inews. I am concerned that mini-inews
and the real inews may disagree on header processing issues. Right now with
CNEWS, header processing is a moving target.

-- 
Stan           internet: sob@bcm.tmc.edu         Director, Networking 
Olan           uucp: rutgers!bcm!sob             and Systems Support
Barber         Opinions expressed are only mine. Baylor College of Medicine