Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!linus!vaxine!wjh12!foxvax1!jim@uw-beaver.UUCP From: jim@uw-beaver.UUCP Newsgroups: net.news.b Subject: Re: Hack to reject articles duplicated due to site name mungeing (sic) Message-ID: <697@uw-beave.UUCP> Date: Tue, 5-Jul-83 19:17:34 EDT Article-I.D.: uw-beave.697 Posted: Tue Jul 5 19:17:34 1983 Date-Received: Thu, 7-Jul-83 14:41:16 EDT References: <229@cdi.UUCP> Lines: 16 Relay-Version:version B 2.10 5/3/83; site wjh12.UUCP Posting-Version:version B 2.10 5/3/83; site uw-beaver Path:wjh12!genrad!linus!philabs!cmcl2!floyd!vax135!cornell!uw-beaver!jim Message-ID:<697@uw-beaver> Date:Tue, 5-Jul-83 19:17:34 EDT Organization:U of Washington Computer Science Caf@cdi's hack to reject dups when the message-id is mangled didn't arrive here intact, but enough of it did arrive that I could see it was intended for sites without DBM. (Correct me if I'm wrong). I have a set of hacks to store the old article-id in the dbm database, while keeping the new message-id in the human-readable history file. This should reject the dups for those of us with DBM. It requires changes to rnews, expire, and cvt.hist. I will test this for a few days, and if it seems to work, will post it.