jbuck@epicen.UUCP (Joe Buck) (11/14/85)
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