Xref: utzoo news.config:1773 news.admin:10680 news.software.b:5854
Path: utzoo!utstat!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!sol.ctr.columbia.edu!cica!iuvax!purdue!haven!decuac!hussar.dco.dec.com!mjr
From: mjr@hussar.dco.dec.com (Marcus J. Ranum)
Newsgroups: news.config,news.admin,news.software.b
Subject: Re: Apology for repostings in alt - 2 C News bugs
Message-ID: <1990Sep25.133959.16472@decuac.dec.com>
Date: 25 Sep 90 13:39:59 GMT
References: <1990Sep24.220833.230@vicom.com>
Sender: news@decuac.dec.com (Network News)
Reply-To: mjr@hussar.dco.dec.com.UUCP (Marcus J. Ranum)
Organization: Digital Equipment Corp., Ultrix Resource Center
Lines: 24

In article <1990Sep24.220833.230@vicom.com> lmb@vicom.com (Larry Blair) writes:

>Bug 2: (or maybe not)

>The path contained in the reposting shows `Path: vsi1!vsi1!...'.  I'm pretty
>sure that 2.11 checked for your site in the path to prevent propagation loops.

	I've been seeing exactly the same problem, and was starting to
wonder if I was hallucinating. [some of our month old+ news has leaked
back out onto the net - thanks to those of you who have pointed this
out] I'm running Cnews, patchlevel "most recent that I know of" :)

	If I post an article with a path like
Path: deucac!decuac.dec.com!decuac!decuac.dec.com!mjr

	it propagagates out just fine.

	We're also getting (though I hope that's fixed, now) articles making
a long, slow loop, and reaching our machine after their history entries have
expired here, and going back around. What's the best way to ensure against
this kind of problem ? I wonder if various Cnews sites have been lucking
out by virtue of Bnews sites "compartmenting" article loops...

mjr.