Article View: news.software.b
Article #4698Re: INN weirdness
From: Rich Salz
Date: Tue, 22 Dec 1992 16:20
Date: Tue, 22 Dec 1992 16:20
14 lines
1215 bytes
1215 bytes
In <hj41Hxpsjb@atlantis.psu.edu> barr@pop.psu.edu (David Barr) writes: > This seems rather odd that INN works like this. I mean, >in what circumstanses would you want not to feed a site a heirarchy >of newsgroups, yet pass control messages for that heirarchy? There are sites that want to see ALL newgroup messages, even if they do not get some groups. Suppose some undergrad posts a message to psu.sex,comp.unix.wizards. Email erupts around the net and a harried sys admin is waken up at 10am to cancel the article. They're tired, and inadvertently post the cancel only to psu.sex. Should the cancel get propagated everywhere, or at least be given the option? INN gives you the tools to be flexible. It's a sharp tool, so you have to be careful and read the documentation. /r$
Technical Details
Message-ID:
<1h7f8oINNn1n@rodan.UU.NET>Path:
arc1-ca.pugleaf.net!sparky!uunet!not-for-mailReferences:
<1h5d6dINNpbp@wintermute.phys.psu.edu> <1h5llbINN414@nic.near.net> <hj41Hxpsjb@atlantis.psu.edu>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!sparky!uunet!not-for-mail From: rsalz@rodan.UU.NET (Rich Salz) Newsgroups: news.software.b Subject: Re: INN weirdness Date: 22 Dec 1992 11:20:40 -0500 Organization: UUNET Technologies Inc, Falls Church, VA Lines: 14 Message-ID: <1h7f8oINNn1n@rodan.UU.NET> References: <1h5d6dINNpbp@wintermute.phys.psu.edu> <1h5llbINN414@nic.near.net> <hj41Hxpsjb@atlantis.psu.edu> NNTP-Posting-Host: rodan.uu.net