Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!wuarchive!cs.utexas.edu!uunet!bfmny0!tneff From: tneff@bfmny0.UU.NET (Tom Neff) Newsgroups: news.sysadmin Subject: Re: clarinet?????? Message-ID: <14809@bfmny0.UU.NET> Date: 27 Oct 89 04:07:26 GMT References: <331@lawnet.LawNet.Com> <2962@splut.conmicro.com> <1989Oct27.023630.29651@brutus.cs.uiuc.edu> Reply-To: tneff@bfmny0.UU.NET (Tom Neff) Organization: ^ Lines: 21 Summary: Expires: Sender: Followup-To: >>Because your upstream feed allows it in their sys file entry for you. They >>either explicitly allow clari.* newsgroups to be sent to you, or (shudder) >>they send you all.* (not the best way to set up a sys file). > >Unless, of course, the site you're feeding explicitly _wants_ all.*. >We're one of those. No particular reason _to_ take everything, but >no reason not to either ... Except that if any of your feeds start taking ClariNet, they've suddenly GOT a good reason not to feed you all.* -- namely, all.* now includes something which you're not paying for and which they're not allowed to pass on if you ain't. So ClariNet and "all.*" in the sys file don't mix well. The downstream site can *accept* all.* if it wants. But if it does so, and if it makes no attempt to regulate what the feed site sends it -- then it has no business complaining when clari.* (or leprosy.*) newsgroups start arriving. -- "Nature loves a vacuum. Digital \O@/ Tom Neff doesn't." -- DEC sales letter /@O\ tneff@bfmny0.UU.NET