Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!uwm.edu!linac!mp.cs.niu.edu!rickert From: rickert@mp.cs.niu.edu (Neil Rickert) Newsgroups: news.software.b Subject: Re: LET'S NAME THE GUILTY POSTING SOFTWARE!!! Message-ID: <1991Jun20.114358.4871@mp.cs.niu.edu> Date: 20 Jun 91 11:43:58 GMT References: <1991Jun19.154645.11885@zoo.toronto.edu> <1991Jun19.172544.32267@mp.cs.niu.edu> <6098@gazette.bcm.tmc.edu> Organization: Northern Illinois University Lines: 32 In article <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. But that is exactly the point. mini-inews does not do the error checking of the REAL inews, but if effectively isolates the poster from the REAL inews making good feedback difficult. 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. Perhaps you want mini-inews submitters to log into their news host occasionally and look in ~news/dead.article to see if their articles were dropped? Any well designed REAL inews which does report errors is going to decide that the report should go to ~news (or whatever uid nntpd runs as) on the news host. >I am afraid that adding more smarts to mini-inews just clouds the real issue. And what is the real issue? Is it that once mini-inews has convinced the news software that the article is submitted by news@news.host, the news software is now unable to discover where it should really complain? -- =*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*= Neil W. Rickert, Computer Science Northern Illinois Univ. DeKalb, IL 60115 +1-815-753-6940