Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2(pesnta.1.3) 9/5/84; site epicen.UUCP
Path: utzoo!watmath!clyde!cbosgd!ihnp4!pesnta!epicen!jbuck
From: jbuck@epicen.UUCP (Joe Buck)
Newsgroups: net.news.adm
Subject: Preserve the usefulness of "net.flame" as a keyword
Message-ID: <269@epicen.UUCP>
Date: Thu, 14-Nov-85 00:34:47 EST
Article-I.D.: epicen.269
Posted: Thu Nov 14 00:34:47 1985
Date-Received: Fri, 15-Nov-85 04:32:43 EST
Distribution: net
Organization: Entropic Processing, Inc., Cupertino, CA
Lines: 18
Summary: put !net.flame in sys; leave net.flame in active

For those sites that don't pass net.flame, may I suggest that you do
it by putting !net.flame in your sys file, but leave net.flame as a
valid newsgroup in your active. Then the "net.flame" keyword stays
attached to the message, so when it gets to my system and I use rn,
I can say
	/net.flame/hj
in flame-prone groups such as net.news.group (or make a global kill
file). If you don't do this, I expect the crosspostings to continue,
but I might read the stuff if there's nothing in the header stating that
it's a flame. I don't allow net.flame on our system, but I don't want
to read net.flame crosspostings either.

Another approach would be to reject an article entirely if ANY group
is net.flame, but that requires software modification.
-- 
Joe Buck				|  Entropic Processing, Inc.
UUCP: {ucbvax,ihnp4}!dual!epicen!jbuck  |  10011 N. Foothill Blvd.
ARPA: dual!epicen!jbuck@BERKELEY.ARPA   |  Cupertino, CA 95014