Xref: utzoo news.software.b:8023 news.admin:14736 Path: utzoo!utgpu!watserv1!watmath!att!linac!midway!mimsy!nocusuhs!nmrdc1!rdc30 From: rdc30@nmrdc1.nmrdc.nnmc.navy.mil (LCDR Michael E. Dobson) Newsgroups: news.software.b,news.admin Subject: Re: Really funny jokes being missed Message-ID: <1991May29.145055.7269@nmrdc1.nmrdc.nnmc.navy.mil> Date: 29 May 91 14:50:55 GMT References: <28357D59.17BB@tct.com> <1991May19.013616.10567@ms.uky.edu> Distribution: na Organization: Naval Medical Research & Development Command Lines: 28 In article <1991May19.013616.10567@ms.uky.edu> kherron@ms.uky.edu (Kenneth Herron) writes: >chip@tct.com (Chip Salzenberg) writes: > >>>> News software which generates articles that do not conform to the RFC is >>>> broken. Articles generated by such buggy software deserve to be discarded. > >One problem with this is that the C-news report only lists the site(s) >which are feeding you bad articles, not where the articles actually >came from or the exact problem with the article. The message IDs are logged >along with the complaint , but the messages themselves are thrown away >(of course) so the concerned administrator has to do a bit of detective work. > grep 'site -' log.o > munged.list gave me the actual message id's of the site generating the article (once I filtered out the duplicate entries). I could then send e-mail to the offending site. I did this for each feed when I was getting lots of bad articles, now that it's slowed to a trickle, it't even easier. >I'm working on a script to notify me of all articles bit-bucketed for >bad header reasons. I could arrange for it to be posted, e.g. to >news.lists. Is there any call for such a thing? You could also post to news.software.b -- Mike Dobson, Sys Admin for | Internet: rdc30@nmrdc1.nmrdc.nnmc.navy.mil nmrdc1.nmrdc.nnmc.navy.mil | UUCP: ...uunet!mimsy!nmrdc1!rdc30 AT&T 3B2/600G Sys V R 3.2.2 | BITNET: dobson@usuhsb or nrd0mxd@vmnmdsc WIN/TCP for 3B2 | MCI-Mail: 377-2719 or 0003772719@mcimail.com