Kenny McCormack
2023-11-19 11:23:15 UTC
The good news: The spam problem (both the so-called "Thai spam" and the
"mushroom spam") is gone from clc and clc++, because Google has (for
reasons of its own) banned both groups. What's funny about this is that
normally people on these groups would be p*ssed off at Google for banning
them, but in this instance, it is a happy coincidence that it stops the
spam. So, we're good with it.
The bad news is that it is still alive and well in many of the other
groups. Right now, comp.editors is getting slammed - about 1 spam per
minute, 24/7.
So, the question becomes, is there any way we can get Google to ban all
newsgroups, not just these 2?
"mushroom spam") is gone from clc and clc++, because Google has (for
reasons of its own) banned both groups. What's funny about this is that
normally people on these groups would be p*ssed off at Google for banning
them, but in this instance, it is a happy coincidence that it stops the
spam. So, we're good with it.
The bad news is that it is still alive and well in many of the other
groups. Right now, comp.editors is getting slammed - about 1 spam per
minute, 24/7.
So, the question becomes, is there any way we can get Google to ban all
newsgroups, not just these 2?
--
The randomly chosen signature file that would have appeared here is more than 4
lines long. As such, it violates one or more Usenet RFCs. In order to remain
in compliance with said RFCs, the actual sig can be found at the following URL:
http://user.xmission.com/~gazelle/Sigs/FreeCollege
The randomly chosen signature file that would have appeared here is more than 4
lines long. As such, it violates one or more Usenet RFCs. In order to remain
in compliance with said RFCs, the actual sig can be found at the following URL:
http://user.xmission.com/~gazelle/Sigs/FreeCollege