CSRPi has been infested with this bullshit for at
least a month now. Constantly-changing addresses,
identities, orgs ... no good way to block 'em
CSRPi has been infested with this bullshit for at
least a month now. Constantly-changing addresses,
identities, orgs ... no good way to block 'em unless
you're writing your own NNTP apps and even then it'd
be a lot of work.
On Mon, 11 Dec 2023 01:15:09 -0500
"56g.1173" <56g.1173@ztq9.net> wrote:
CSRPi has been infested with this bullshit for at
least a month now. Constantly-changing addresses,
identities, orgs ... no good way to block 'em unless
you're writing your own NNTP apps and even then it'd
be a lot of work.
First I've heard of it - cleanfeed must be suppressing it at E-S.
CSRPi has been infested with this bullshit for at
least a month now. Constantly-changing addresses,
identities, orgs ... no good way to block 'em unless
you're writing your own NNTP apps and even then it'd
be a lot of work.
On Mon, 11 Dec 2023 01:15:09 -0500
"56g.1173" <56g.1173@ztq9.net> wrote:
CSRPi has been infested with this bullshit for at
least a month now. Constantly-changing addresses,
identities, orgs ... no good way to block 'em unless
you're writing your own NNTP apps and even then it'd
be a lot of work.
First I've heard of it - cleanfeed must be suppressing it at E-S.
CSRPi has been infested with this bullshit for at
least a month now. Constantly-changing addresses,
identities, orgs ... no good way to block 'em unless
you're writing your own NNTP apps and even then it'd
be a lot of work.
56g.1173 <56g.1173@ztq9.net> wrote:
CSRPi has been infested with this bullshit for at
least a month now. Constantly-changing addresses,
identities, orgs ... no good way to block 'em unless
you're writing your own NNTP apps and even then it'd
be a lot of work.
Sounds like the Google Groups spam has reached here then. For
background see news.admin.net-abuse.usenet.
You're using Thunderbird, and I believe many other Thunderbird
users have killfiled all posts originating from Google Groups as a
solution, but perhaps that's not what you'd call a "good way to
block 'em".
Many news servers have also started implementing spam filtering,
or blocking all posts from Google Groups like the one I'm using
did.
Alas there are also GOOD posts from people (foolishly)
using GoogGroups. Don't want to burn them
CSRPi has been infested with this bullshit for at least a month
now. Constantly-changing addresses, identities, orgs ... no good way
to block 'em unless you're writing your own NNTP apps and even then
it'd be a lot of work.
Usenet ain't what it used to be. Indeed it's just BARELY hanging
on. Goog thinks it OWNS Usenet. Most ISPs no longer provide it because
of "liability" issues for free speech/ideas/(and PORN).
I’m not ready to block Google locally; it’s a major source of legitimate user as well as spam. But when I look at my logs I do see where the
people advocating a full block are coming from:
On 2023-12-12, Richard Kettlewell <invalid@invalid.invalid> wrote:
I’m not ready to block Google locally; it’s a major source of legitimate >> user as well as spam. But when I look at my logs I do see where the
people advocating a full block are coming from:
<list snipped>
I took a close look at some of this spam, and found that it
contains an "Injection-Info: google..." header that isn't
in legitimate messages, whether they're from a Google user
or not. By adding the following stanza to ~/News/Score
(I'm using slrn), I'm able to drop the spam while retaining
legitimate messages with gmail.com on the From: line.
[comp.*.*]
Score: =-9999
Expires: 9/14/2024
Injection-Info: google*
Newsgroup: comp\.*\.*
Charlie Gibbs wrote:
I took a close look at some of this spam, and found that it
contains an "Injection-Info: google..." header that isn't
in legitimate messages, whether they're from a Google user
or not.
Fore some reason injection info didnt work on thunderbird, but message
ID contains googlegroups did IIRC.
On 2023-12-12, Richard Kettlewell <invalid@invalid.invalid> wrote:
I’m not ready to block Google locally; it’s a major source of legitimate >> user as well as spam. But when I look at my logs I do see where the
people advocating a full block are coming from:
<list snipped>
I took a close look at some of this spam, and found that it
contains an "Injection-Info: google..." header that isn't
in legitimate messages, whether they're from a Google user
or not. By adding the following stanza to ~/News/Score
(I'm using slrn), I'm able to drop the spam while retaining
legitimate messages with gmail.com on the From: line.
[comp.*.*]
Score: =-9999
Expires: 9/14/2024
Injection-Info: google*
Newsgroup: comp\.*\.*
Charlie Gibbs <cgibbs@kltpzyxm.invalid> wrote:
On 2023-12-12, Richard Kettlewell <invalid@invalid.invalid> wrote:
I’m not ready to block Google locally; it’s a major source of legitimate
user as well as spam. But when I look at my logs I do see where the
people advocating a full block are coming from:
<list snipped>
I took a close look at some of this spam, and found that it
contains an "Injection-Info: google..." header that isn't
in legitimate messages, whether they're from a Google user
or not. By adding the following stanza to ~/News/Score
(I'm using slrn), I'm able to drop the spam while retaining
legitimate messages with gmail.com on the From: line.
[comp.*.*]
Score: =-9999
Expires: 9/14/2024
Injection-Info: google*
Newsgroup: comp\.*\.*
Any idea how I might do this with tin, or do I need to shitcan tin and replace it with something else? Its filtering appears to be restricted to a handful of common header lines (such as From and Subject) and doesn't appear to allow filtering on just any header line. What little documentation I've been able to find has been woefully inadequate.
(I'd been using trn (and rn before that) for decades, but it hasn't been updated in nearly as long and I can't get it to build on reasonably modern Gentoo Linux systems anymore.)
Charlie Gibbs <cgibbs@kltpzyxm.invalid> wrote:
On 2023-12-12, Richard Kettlewell <invalid@invalid.invalid> wrote:
I’m not ready to block Google locally; it’s a major source of legitimate
user as well as spam. But when I look at my logs I do see where the
people advocating a full block are coming from:
<list snipped>
I took a close look at some of this spam, and found that it
contains an "Injection-Info: google..." header that isn't
in legitimate messages, whether they're from a Google user
or not. By adding the following stanza to ~/News/Score
(I'm using slrn), I'm able to drop the spam while retaining
legitimate messages with gmail.com on the From: line.
[comp.*.*]
Score: =-9999
Expires: 9/14/2024
Injection-Info: google*
Newsgroup: comp\.*\.*
Any idea how I might do this with tin, or do I need to shitcan tin and replace it with something else? Its filtering appears to be restricted to a handful of common header lines (such as From and Subject) and doesn't appear to allow filtering on just any header line. What little documentation I've been able to find has been woefully inadequate.
56g.1173 wrote:
Alas there are also GOOD posts from people (foolishly)
using GoogGroups. Don't want to burn them
you appear to be using thunderbird (even though it's an old version, all
of the following should apply)
create a new address book, e.g. called "googlegroups-whitelist", add all
the good authors email addrs to it
Far too much work - and highly discriminatory against
those I don't already KNOW to post useful stuff (even
if they ARE annoying
56g.1183 wrote:
Far too much work - and highly discriminatory against
those I don't already KNOW to post useful stuff (even
if they ARE annoying
Well, google are soon going to do it for you, all their users will be indiscriminately dumped.
all those who care about Usenet will find another way to post.
The Natural Philosopher wrote:
all those who care about Usenet will find another way to post.
You'd think, but I've seen a few users (who presumably used a client and
had an account on a server before google took deja) say they can't be bothered if it's more involved than a web page ...
On 21 Dec 2023 at 10:58:30 GMT, "Andy Burns" <usenet@andyburns.uk> wrote:
The Natural Philosopher wrote:
all those who care about Usenet will find another way to post.
You'd think, but I've seen a few users (who presumably used a client and
had an account on a server before google took deja) say they can't be
bothered if it's more involved than a web page ...
Well knickers to 'em then.
56g.1183 wrote:
Far too much work - and highly discriminatory against
those I don't already KNOW to post useful stuff (even
if they ARE annoying
Well, google are soon going to do it for you, all their users will be indiscriminately dumped.
On 21/12/2023 11:33, TimS wrote:
On 21 Dec 2023 at 10:58:30 GMT, "Andy Burns" <usenet@andyburns.uk> wrote:I tend to concur with that sentiment.
The Natural Philosopher wrote:
all those who care about Usenet will find another way to post.
You'd think, but I've seen a few users (who presumably used a client and >>> had an account on a server before google took deja) say they can't be
bothered if it's more involved than a web page ...
Well knickers to 'em then.
I took a close look at some of this spam, and found that it
contains an "Injection-Info: google..." header that isn't
in legitimate messages, whether they're from a Google user
or not. By adding the following stanza to ~/News/Score
(I'm using slrn), I'm able to drop the spam while retaining
legitimate messages with gmail.com on the From: line.
[comp.*.*]
Score: =-9999
Expires: 9/14/2024
Injection-Info: google*
Newsgroup: comp\.*\.*
| Sysop: | Xerxes |
|---|---|
| Location: | Azle, Texas |
| Users: | 119 |
| Nodes: | 10 (1 / 9) |
| Uptime: | 151:34:34 |
| Calls: | 3,034 |
| Calls today: | 2 |
| Files: | 156 |
| U/L today: |
0 files (0K bytes) |
| D/L today: |
0 files (0K bytes) |
| Messages: | 294,347 |
| Posted today: | 0 |