Xref: utzoo news.admin:14973 news.software.b:8140
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!swrinde!cs.utexas.edu!uunet!zephyr.ens.tek.com!uw-beaver!milton!sumax!polari!rwing!fnx!news
From: news@fnx.UUCP (News Administrator)
Newsgroups: news.admin,news.software.b
Subject: Possible solution to C news dropping articles?
Message-ID: <1024@fnx.UUCP>
Date: 5 Jun 91 19:48:54 GMT
References: <1991May31.145603.10105@sceard.Sceard.COM> <244y314w164w@mantis.co.uk>
Followup-To: news.admin
Organization: I/Ovations    Kirkland, WA
Lines: 12

In article <244y314w164w@mantis.co.uk> mathew@mantis.co.uk (Giving C News a *HUG*) writes:
>As I have mentioned several times, I did all of this. The software I was
>using was perfectly OK according to every test I was able to do from here. I
>didn't get any error reports, I didn't notice anything untoward. Postings to
>misc.test using the 'bad' software worked -- I got responses.

So, I have an idea.  Why doesn't someone cobble up a test suite using the
appropriate pieces of Cnews code?  A site could then run the test suite
on a sample article to see if some site down the line would dump it on the
floor.  This way Henry, et al. don't have to do inelegant things to their
software, and anybody that cares if their articles get out to the world
have a way to check their software.