🚀 go-pugleaf

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?

Standard?  What standard?  One common standard is 'throw them away,
they're only news anyway'.

What I do, which normally rescues (at least most of) the 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.

Second try:  On rare occasion, that fails.  In this case, the problem
is usually that some article has, somehow, changed size, so that the
'article length' lines don't match reality, and relaynews (or whoever)
gets out of sync.  From the message sent to you (the usenet guru) you
can identify which message it was.  Then, edit the bad file to remove
the offending article (which you do lose), taking out everything from
(and including) the '#! rnews <number>' line before it, down to (but
NOT including) the '#! rnews <number>' line after it.  Then move it
back up into in.coming.

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

-- 
Paul Smee, Computing Service, University of Bristol, Bristol BS8 1UD, UK
 P.Smee@bristol.ac.uk - ..!uunet!uknet!bsmail!p.smee - Tel +44 272 303132