"DoN. Nichols" wrote in message
...
According to Doug Miller :
In article , steamer
wrote:
--Please post text string for the kill; I'm not all that skilled
in
unix and I suspect neither are a pile of others who are getting this
stuff.

Just filter out anything that's crossposted to sci.crypt . That group is
the
real target of this flood.

It depends (somewhat) on your newsreader. With mine (trn), in
the killfile specific for rec.crafts.metalworking I have the following
line as the first active line:

================================================== ====================
/: .*sci.crypt/h:j
================================================== ====================

the "/h:j" says "Look anywhere in the headers (since it does not seem to
have a specific entry for the "Newgroups: " header line), for anything
which has some unknown count of other characters ".*" followed by
"sci.crypt", and "junk" (mark as already read) those which match.

There are other one which check the "From: " header "/f:", and
without any specifier, it assumes that you are only killfiling on the
"Subject: " header.

I suspect that most unix newsreaders have similar killfiles, but
there may be details which are different.

Note that the killfile change won't do anything with articles
which the newsreader already knows about (unless you fake it into
thinking that it does not know about them), but it will zap the new ones
as they are discovered.

In trn, you can edit the killfile (using either vi by default,
or whatever editor you have indicated in the EDITOR environment
variable) by typing '^K" (control-K). Or -- you can find where it
stores the killfile on your system. There can be a global killfile for
those who are trying to read two or more newsgrops which are under
attack at the same time.

Good Luck,
DoN.

I was getting aggravated with this childish bull****. I had put "," in the
specified newsgroups portion of my filter. But still, I was getting sporge.
Today, I installed RegistryFix which I had done on my other computers. I
did a scan and it had over 500 problems.

Then I went to newsgroups again, and all I got was messages specific to that
newsgroup. After this goes away, I'll remove the comma from newsgroup
rules, and get back to normal.

I think there should be some hefty fines and jail time for people who would
interrupt interstate communications like this. It doesn't seem that hard to
find out who's doing it, but I guess it's down on the list of priorities.

Too bad shooting, castration and hanging has been shunned by society. A
couple of those, and the problems would go away quickly.

Steve