Path: utzoo!yunexus!geac!eric
From: eric@geac.UUCP (Eric Dirks)
Newsgroups: tor.news
Subject: Re: Corruption of local news
Message-ID: <6334@geac.UUCP>
Date: 17 Jan 89 18:20:22 GMT
Article-I.D.: geac.6334
References: <34476@bbn.COM> <1989Jan14.015454.2767@sq.uucp> <3749@attcan.UUCP> <1989Jan16.083615.2874@utzoo.uucp> <4821@mnetor.UUCP>
Reply-To: eric@geac.UUCP (Eric Dirks)
Followup-To: tor.news
Distribution: tor
Organization: Geac Computer Corporation
Lines: 24

In article <4821@mnetor.UUCP> ron@mnetor.UUCP (Ron Miller) writes:
>In article <2874@utzoo.uucp>, henry@utzoo.uucp (Henry Spencer) writes:
>>In article <3749@attcan.UUCP> bob@attcan.UUCP (Bob Kyryliuk) writes:
>>>>The article I checked has Message-Id "<34476@bbn.COM>" and Subject "CALL

>> It's clean on utzoo.

>It's clean on mnetor too.

This means that there are problems in the mnetor->geac link. I would like to 
know if it is only articles we get from mnetor that are affected. Has anyone
found any problems with articles that have not passed through via mnetor->geac 
path.  (eg yunexus->geac-> ...)

Does anyone know of an easy way of locating these corrupt files? I don't think
grep accepts control characters.




-- 
Eric Dirks 		Geac Computer Corporation, Markham, Ontario
eric@geac
{uunet!mnetor,yunexus,utgpu}!geac!eric