🚀 go-pugleaf

In the referenced article, P.Smee@bristol.ac.uk (Paul Smee) writes:
>In article <BzBoE0.6pG@avalon.nwc.navy.mil> dejesus@archimedes.nwc.navy.mil (Francisco X DeJesus) writes:
>>What is the "standard" thing to do with news batch files that end up
>>in the incoming/bad directory? How do I force my news system to process
>>these files and extract/store the individual articles?

>First try:  Just move the file from in.coming/bad back up into
>in.coming.  Usually this works.  Usually the blowup will have been
>caused by a bad control message, but the news system seems to have
>already, by then, made the history entry saying it's seen that control
>message, so on the second time through it gets ignored as a 'duplicate'
>and everything goes in fine.

Cnews will process the entire batch on the first attempt. The fact that
you get no error message the second time is because (as Paul says) it
has already been processed and is therfore discarded. There is no need
to ask Cnews to re-process it, you have already got all the good articles
out of the batch.

>Second try:
(edit the batch to remove the single bad article if possible).
Good advice, but usually this will only get you one extra article, the
one following the bad one, and only then if the bad article is shorter than
its byte count in the #!rnews header implies.

>If none of that works, just drop it on the floor.

Good advice. It is only news after all!