I see this NG is also being attacked by spammers,
I guess google really wants to muzzle it.

bad sector wrote:

> I see this NG is also being attacked by spammers

I don't see it unless I view the relevant tag.

In comp.mobile.android, on Sun, 3 Dec 2023 15:14:37 +0000, Andy Burns
<usenet@andyburns.uk> wrote:

>bad sector wrote:
>
>> I see this NG is also being attacked by spammers
>
>I don't see it unless I view the relevant tag.

What's a "relevant tag"?

I see it. If someone posts at the same time they do, I'm lucky if I
don't delete a real post/thread when I delete the spam. Like this
thread.

micky wrote:

> Andy Burns wrote:
>
>> bad sector wrote:
>>
>>> I see this NG is also being attacked by spammers
>>
>> I don't see it unless I view the relevant tag.
>
> What's a "relevant tag"?

I use thundberbird message filters to add tag #6 to messages coming from
googlegroups (unless it's from someone in a special address book) that
way I don't see it. But if I want to check whether the filters are
working, I can view all messages with tag #6

Am 03.12.23 um 16:12 schrieb bad sector:
>
>
> I see this NG is also being attacked by spammers,
> I guess google really wants to muzzle it.

Here it is absolutely spamfree.

Your client - albeit so old it already turned to dust - would easily
allow you to filter it. Or use Solani, E-S or individual.net.

--
"Gutta cavat lapidem." (Ovid)

Andy Burns <usenet@andyburns.uk> wrote

>> I see this NG is also being attacked by spammers
>
> I don't see it unless I view the relevant tag.

It's a big problem lately... hundreds upon hundreds of spams per day...
And getting worse by the day...

When Google won't even let me log into my own email from a VPN, you'd think
that these hundreds upon hundreds of spams would be blocked by Google.
<http://groups.google.com/g/comp.mobile.android>

I can't fathom how Google's coding is so sophomoric, that it doesn't.
Having built procmail scripts in the olden days, I have never thought that
Google's coders were any good given they simply block everything in email.

But then why can't they block this spam flooding us by hundreds a day?
<https://i.postimg.cc/6pj29c6f/spam01.jpg>
How can even Google's lousy coders be _that_ atrocious? I don't know.

Even I could block that spam (although I only have the likes of Alan Baker,
Snit, Dustin Cook, Rod Speed, and a couple of others in my killfiles).

Why can't Google? (if it's going through them, that is). On this newsgroup,
Frank is the acknowledged leader in nntp headers so maybe he'll chime in.

Unfortunately, there are many hundreds a day now, seemingly from spammers
who want us to watch movies for the most part, or to click their links.

The headers of the few I sampled "appear" to come from Google Groups, but,
of course, headers can be forged - but even so - it's a consistent header.

Many people block Google Groups posts, out of hand, so that's one possible
solution (I only randomly sampled the headers) and it could be that those
headers are injected anyway - so then it's up to the NNTP admins to do it.

For us, if we agree not to use the word "watch" or "movies" in the subject,
that will get some of them, but I think just blocking en masse headers
indicating Google Groups will do the trick.

It's sad that we finally have to implement spam filters to do this though.
Here is just one header out of many hundreds that came in today...

What do folks who know more than I do about headers make of it?

X-Received: by 2002:a37:ad0a:0:b0:77d:ccba:990f with SMTP id
f10-20020a37ad0a000000b0077dccba990fmr385141qkm.8.1701619779751; Sun, 03
Dec 2023 08:09:39 -0800 (PST)
X-Received: by 2002:aca:1011:0:b0:3b8:950b:6e8c with SMTP id
17-20020aca1011000000b003b8950b6e8cmr1433560oiq.4.1701619779506; Sun, 03
Dec 2023 08:09:39 -0800 (PST)
Path:
news.mynewsserver.net!3.eu.feeder.erje.net!1.us.feeder.erje.net!feeder.erje.net!usenet.blueworldhosting.com!diablo1.usenet.blueworldhosting.com!peer03.iad!feed-me.highwinds-media.com!news.highwinds-media.com!news-out.google.com!nntp.google.com!postnews.google.com!google-groups.googlegroups.com!not-for-mail
Newsgroups: comp.mobile.android
Date: Sun, 3 Dec 2023 08:09:39 -0800 (PST)
In-Reply-To: <da1978f5-574f-42f0-bc35-71a15fa68c8an@googlegroups.com>
Injection-Info: google-groups.googlegroups.com;
posting-host=2a0f:e383:4952:74ab:855a:dfee:749a:6576;
posting-account=cd0JhgoAAACShHBEpPkoEjnWjSQ47bCx
NNTP-Posting-Host: 2a0f:e383:4952:74ab:855a:dfee:749a:6576
References: <da1978f5-574f-42f0-bc35-71a15fa68c8an@googlegroups.com>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <aaa508ab-0864-4f0c-9b95-a7db21e733cfn@googlegroups.com>
Subject: Re: WATCH! Holiday Twist (2023) FullMovie Free Online Mp4 On
123????????????
From: Derrick Matthews <derrickmatthews946@gmail.com>
Injection-Date: Sun, 03 Dec 2023 16:09:39 +0000
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Received-Bytes: 5271
Xref: sewer comp.mobile.android:110187

Wally J wrote:

> Even I could block that spam [...] Why can't Google? (if it's going
> through them, that is).

It's not only going through them, it's coming *from* their users.

> On this newsgroup, Frank is the acknowledged
> leader in nntp headers so maybe he'll chime in.

I have a separate address book called "google whitelist"
I put people in it of I know they're google groups users

I have a message filter that has two rules and two actions

IF "from" ISN'T IN ADDR BOOK "google whitelist"
AND message-id CONTAINS "@googlegroups.com"
THEN mark as read
AND add tag #6

That's thunderbird, I'm sure other clients can do similar

Andy Burns <usenet@andyburns.uk> wrote

> I use thundberbird message filters to add tag #6 to messages coming from
> googlegroups (unless it's from someone in a special address book) that
> way I don't see it. But if I want to check whether the filters are
> working, I can view all messages with tag #6

There are so many hundreds coming in, and getting worse by the day, that
the process I've used so far (manual select & delete) won't work, as I
almost deleted this thread in that process (which micky also alluded to).

I never thought much of Google's coding skills when it comes to blocking
spam (they just block everything) so I suspect these are not actually
coming from Google Groups (but folks like Frank may know better than I
since he used to run an nntp server for his old company, as I recall).

However... the spam may not be coming from Google Groups at all... as you
can note their injected headers (in my case) are above the PATH: directive.

I suspect the spammers set up an nntp server, and they were able to get
peered, so part of the solution is in the peering groups, such as:
<http://groups.google.com/g/news.admin.peering>
<http://groups.google.com/g/news.software.nntp>
(I'm not sure which the canonical peering group is though.)

For individuals like micky who need help setting up filters, there is a
newsgroup just for newsreaders that he can post his questions to.
<http://groups.google.com/g/news.software.readers>

And then there are sometimes individual groups for specific newsreaders.
<http://groups.google.com/g/alt.comp.software.thunderbird>
--
Note I didn't test these urls today so some above urls might not work.

On 12/3/23 10:59 AM, Jörg Lorenz wrote:
> Am 03.12.23 um 16:12 schrieb bad sector:
>>
>>
>> I see this NG is also being attacked by spammers,
>> I guess google really wants to muzzle it.
>
> Here it is absolutely spamfree.
>
> Your client - albeit so old it already turned to dust - would easily
> allow you to filter it. Or use Solani, E-S or individual.net.

Sticking one's head in the sand doesn't impede google,
and no one else is behind all the spam as far as I'm
concerned because no one else wants to destroy usenet
as much as google does. The prime beneficiary has to
be the prime suspect. The same problem on many, many
other NG's and no one is going to convince me that
spammers would be so attracted by a dying platform.

Andy Burns <usenet@andyburns.uk> wrote

>> Even I could block that spam [...] Why can't Google? (if it's going
>> through them, that is).
>
> It's not only going through them, it's coming *from* their users.

Hi Andy,

I'm actually a bit confused by the enormity of this spam coming in...

I'm not so sure, but I readily admit I don't know as much about headers as
people like you or Stan or Frank Slootweg would (hell, I don't even know
how to look up an ivp6 IP address, which these headers seem to be using).

The reason I'm not so sure is that there are hundreds upon hundreds of
them, and even Google's terrible coders wouldn't be _that_ stupid to let
that happen (when I can't even sign into my own email using a VPN anyway).

I'm not sure though, because if it _is_ coming from Google's users, then
Google coders suck more than I thought they did, in terms of spam filters.

NOTE: I think Google's coders on tracking us are brilliant; so my opinion
of Google's coders stems from the way they block too much in my email.

However, I will affirm that it really does not matter to us, as
individuals, where the spam is coming from as we all have to block the spam
based on what is in the headers (or body) alone - which "appear" to be
coming from Google's users.

>> On this newsgroup, Frank is the acknowledged
>> leader in nntp headers so maybe he'll chime in.
>
> I have a separate address book called "google whitelist"
> I put people in it of I know they're google groups users

Yeah. I know how it works. What I'm wondering is why the news servers are
peering this crap. That is really where the fundamental filters should be.

Why does it show up in a Google Groups listing, for example?
<http://groups.google.com/g/comp.mobile.android>

You'd think Google would filter that spam out, wouldn't you?
(I don't understand why it's in that URL ouput because it should not be!)
> I have a message filter that has two rules and two actions
>
> IF "from" ISN'T IN ADDR BOOK "google whitelist"
> AND message-id CONTAINS "@googlegroups.com"
> THEN mark as read
> AND add tag #6

This is great! People like you can help those who are on TB!
It should be cut-and-paste for them.

I think Vanguard is on Dialog, so he can help the dialog users too.
Best is if he provides a script that others can just cut-and-paste.

Both have fantastic filtering capabilities, albeit some are cryptic syntax.

> That's thunderbird, I'm sure other clients can do similar

I'm well aware of filters and I'm as well aware that every newsreader has
its own method for implementing them - but that information above is useful
for folks like micky who probably would need help.

As for me, I can filter on anything as my filters use regex methods.
It's just a PITA to set it up.

Did you ever set up procmail filters, Andy?
My setup is like that (not the same, but similar in form & function).

It's a PITA.
It's not as easy as just deleting anything that comes from Joerg.

But you have a good starting point which is (pseudocode)
If it's not in the whitelist, and
if the message-id contains "@googlegroups.com"
then delete it

My newsreader scripts don't have a whitelist though, so for me, if the
message-id has "@googlegroups.com", then I will be wiping it out.

Is there anyone on the Android newsgroup who posts from Google Groups?

In comp.mobile.android, on Sun, 3 Dec 2023 15:49:22 +0000, Andy Burns
<usenet@andyburns.uk> wrote:

>micky wrote:
>
>> Andy Burns wrote:
>>
>>> bad sector wrote:
>>>
>>>> I see this NG is also being attacked by spammers
>>>
>>> I don't see it unless I view the relevant tag.
>>
>> What's a "relevant tag"?
>
>I use thundberbird message filters to add tag #6 to messages coming from
>googlegroups (unless it's from someone in a special address book) that
>way I don't see it. But if I want to check whether the filters are
>working, I can view all messages with tag #6

Very interesting. Copy to a friend who uses Thunderbird.

micky <NONONOmisc07@fmguy.com> wrote

> Very interesting. Copy to a friend who uses Thunderbird.

Hi micky,

To help you (and others like you) out...

1. Best to point your friends on TB to the TB Usenet newsgroup.
alt.comp.software.thunderbird
They will answer TB & BetterBird filtering questions.

One set of web-searchable permanent auto-archives are here:
<http://alt.comp.software.thunderbird.narkive.com>

2. And if you're really using Forte as your newsreader...
I think Ken Blake uses Forte so you can ask him for help.

I think this is the group for the forte newsreader questions.
alt.usenet.offline-reader.forte-agent (if you can believe that)
There are other groups with "forte" in the name though.

The very top-most post is "Google spam" in fact, just now:
<https://groups.google.com/g/alt.usenet.offline-reader.forte-agent>
From: John Larkin
Dec 2, 2023, 9:53:45 PM (16 hours ago)
Does anyone know the proper filter expression to kill all
usenet posts from google groups?
3. There's also a Usenet newsgroup for all newsreader support.
news.software.readers
<https://groups.google.com/g/news.software.readers>

Frank and Vanguard often post to that newsgroup to help others.
--
I didn't doublecheck all the URLs but they should be close.

bad sector <forgetski@invalid.net> wrote:
> On 12/3/23 10:59 AM, Jörg Lorenz wrote:
> > Am 03.12.23 um 16:12 schrieb bad sector:
> >>
> >>
> >> I see this NG is also being attacked by spammers,
> >> I guess google really wants to muzzle it.
> >
> > Here it is absolutely spamfree.
> >
> > Your client - albeit so old it already turned to dust - would easily
> > allow you to filter it. Or use Solani, E-S or individual.net.
>
> Sticking one's head in the sand doesn't impede google,
> and no one else is behind all the spam as far as I'm
> concerned because no one else wants to destroy usenet
> as much as google does. The prime beneficiary has to
> be the prime suspect. The same problem on many, many
> other NG's and no one is going to convince me that
> spammers would be so attracted by a dying platform.

This has been and is being discussed at length in the abuse and News
admin groups.

The concensus is that Google isn't even aware of the problems and
doesn't care about/for their Google Groups to Usenet gateway. So we can
scream and yell all we want, Google isn't listening.

The 'best' Google does is that if someone gets through to them somehow
about abuse in a particular group, they make that group read-only,
killing not only the spam (in only *that* group), but also killing any
legit Google Groups posters in that group. Did I already say that Google
doesn't care?

News admins are trying to filter the spam while keeping the legit
posts (from GG users), but it's an endless job.

In the old days, we would issue an UDP (Usenet Death Penalty), but an
UDP doesn't work against some entity which isn't listening and doesn't
care.

--
Frank Slootweg, ex (part time) News admin in some tiny 150K employee company.

bad sector <forgetski@invalid.net> wrote

>> Your client - albeit so old it already turned to dust - would easily
>> allow you to filter it. Or use Solani, E-S or individual.net.
>
> Sticking one's head in the sand doesn't impede google,
> and no one else is behind all the spam as far as I'm
> concerned because no one else wants to destroy usenet
> as much as google does. The prime beneficiary has to
> be the prime suspect. The same problem on many, many
> other NG's and no one is going to convince me that
> spammers would be so attracted by a dying platform.

It's worse than I had originally thought it was gonna be.

I wrote to the folks on the peering newsgroups who are
convinced this is coming from Google servers unfortunately.
*Who is peering all these spams ostensibly from Google Groups?*
<https://groups.google.com/g/news.admin.peering/c/AgrNUeZuAkw>

The problem is the following, as they seem to see it.
1. The spam is coming from Google servers
2. The peers are nntp servers such as news.highwinds-media.com

That's bad.
a. You can't ever get anyone in Mountainview to care
b. Same with Highwinds (they love spammers who pay money)

Still, the problem has to be solved in this order:
1. Google
2. Peers
3. Users

As users, the news.software.nntp folks told me this header
can't be forged so it's something we personally can filter
on the "Injection-Info:" header, which they say can't be
forged.

I tried forging it but I got the error each time of:
"Posting article failed: Can't set system Injection-Info: header"

That means we can individually filter on this header alone:
Injection-Info: google-groups.googlegroups.com;

I hate doing things that brainless as to filter out ALL posts
from Google Groups, so I'm hoping there is a way to get a hold
of someone in Mountainview by phone or email who gives a hoot.

Is there?

Frank Slootweg <this@ddress.is.invalid> wrote

> The 'best' Google does is that if someone gets through to them somehow
> about abuse in a particular group, they make that group read-only,
> killing not only the spam (in only *that* group), but also killing any
> legit Google Groups posters in that group. Did I already say that Google
> doesn't care?

Hi Frank,

I had posted my query earlier to n.a.p & to n.s.n, where the likes of Marco
Moock & Grant Taylor (both of whom you know well), told me the situation.
*Who is peering all these spams ostensibly from Google Groups?*
<https://groups.google.com/g/news.software.nntp/c/p4NgdFEMeIU>

As I see it, the problem can only be solved in this order:
1. Google (who is nearly impossible to communicate with)
2. Peers (like highwinds, the assholes that they are)
3. Users

Starting in order...

I have had success with getting Google to fix Maps (but they care about
that product) but since I happen to live relatively near Mountainview,
maybe I can pay them a visit?

Do those groups you speak of have a _contact_ at Google I can try to reach?

Wally J <walterjones@invalid.nospam> wrote

> As I see it, the problem can only be solved in this order:
> 1. Google (who is nearly impossible to communicate with)
> 2. Peers (like highwinds, the assholes that they are)
> 3. Users

I had a long conversation with the folks on the nntp & peering ngs.
They say Google doesn't care. Nor do the peers like Highwinds & Giganews.
So it may be up to each of us.

But that's crazy.
One person should write the filter (who knows the tool inside & out).
And the rest of the people should just copy it and use it.

Here's a web site trying to do something about it to help users implement
the filter since it's best if one person implements it & the others copy.
<http://twovoyagers.com/improve-usenet.org/index.html>

On 2023-12-04 08:57, Wally J wrote:
> Wally J <walterjones@invalid.nospam> wrote
>
>> As I see it, the problem can only be solved in this order:
>> 1. Google (who is nearly impossible to communicate with)
>> 2. Peers (like highwinds, the assholes that they are)
>> 3. Users
>
> I had a long conversation with the folks on the nntp & peering ngs.
> They say Google doesn't care. Nor do the peers like Highwinds & Giganews.
> So it may be up to each of us.
>
> But that's crazy.
> One person should write the filter (who knows the tool inside & out).
> And the rest of the people should just copy it and use it.
>
> Here's a web site trying to do something about it to help users implement
> the filter since it's best if one person implements it & the others copy.
> <http://twovoyagers.com/improve-usenet.org/index.html>

Filtering out all of Google Groups locally is trivial.

Just delete mail or delete subthreads (your choice) when
User-Agent is "G2/1.0".

Filtering only the spam is hard: clients like Thunderbird lack spam
filters on the nntp side. You can do filters to remove spam that matches
some pattern, but not changing patterns.

Servers like News.Individual.NET are filtering out the Google spam (or
most of it), with a small delay, so moving to those servers is other
thing that users can do.

But IMO, the best thing to do would be to disconnect Usenet servers from
Google, so that Google can not send nor receive from Usenet. That might
force them to investigate and talk. Might. If they don't, who cares.

--
Cheers,
Carlos E.R.

On Sun, 3 Dec 2023 16:59:07 +0100, Jörg Lorenz wrote:
> Am 03.12.23 um 16:12 schrieb bad sector:
>>
>> I see this NG is also being attacked by spammers,
>> I guess google really wants to muzzle it.
>
> Here it is absolutely spamfree.
>
> Your client - albeit so old it already turned to dust - would easily
> allow you to filter it. Or use Solani, E-S or individual.net.

+1 => individual.net

I did not know this ng was being spammed until I saw today's posts.

Carlos E. R. <robin_listas@es.invalid> wrote:
> On 2023-12-04 08:57, Wally J wrote:
> > Wally J <walterjones@invalid.nospam> wrote
> >
> >> As I see it, the problem can only be solved in this order:
> >> 1. Google (who is nearly impossible to communicate with)
> >> 2. Peers (like highwinds, the assholes that they are)
> >> 3. Users
> >
> > I had a long conversation with the folks on the nntp & peering ngs.
> > They say Google doesn't care. Nor do the peers like Highwinds & Giganews.
> > So it may be up to each of us.
> >
> > But that's crazy.
> > One person should write the filter (who knows the tool inside & out).
> > And the rest of the people should just copy it and use it.

The News admins of the well-managed servers already made tools and are
sharing them amongst themselves. The main method used is NoCeM (No See
'Em).

'The NoCeM FAQ'
<http://www.cm.org/faq.html>

> > Here's a web site trying to do something about it to help users implement
> > the filter since it's best if one person implements it & the others copy.
> > <http://twovoyagers.com/improve-usenet.org/index.html>
>
> Filtering out all of Google Groups locally is trivial.
>
> Just delete mail or delete subthreads (your choice) when
> User-Agent is "G2/1.0".

Exactly. While the News admins are trying to do their bit, we users
can do our bit, by filtering any remaining Google Groups posts and - if
wanted - whitelisting the good (GG) guys.

> Filtering only the spam is hard: clients like Thunderbird lack spam
> filters on the nntp side. You can do filters to remove spam that matches
> some pattern, but not changing patterns.
>
> Servers like News.Individual.NET are filtering out the Google spam (or
> most of it), with a small delay, so moving to those servers is other
> thing that users can do.

AFAIK, News.Individual.NET uses the above mentioned NoCeM method.

> But IMO, the best thing to do would be to disconnect Usenet servers from
> Google, so that Google can not send nor receive from Usenet. That might
> force them to investigate and talk. Might. If they don't, who cares.

Sofar, the consensus amongst the News admins is that they care enough
about the legit Google Groups posters to continue filtering the (GG
originated) spam from their servers.

Wally J <walterjones@invalid.nospam> wrote:
> Frank Slootweg <this@ddress.is.invalid> wrote
>
> > The 'best' Google does is that if someone gets through to them somehow
> > about abuse in a particular group, they make that group read-only,
> > killing not only the spam (in only *that* group), but also killing any
> > legit Google Groups posters in that group. Did I already say that Google
> > doesn't care?
>
> Hi Frank,
>
> I had posted my query earlier to n.a.p & to n.s.n, where the likes of Marco
> Moock & Grant Taylor (both of whom you know well), told me the situation.
> *Who is peering all these spams ostensibly from Google Groups?*
> <https://groups.google.com/g/news.software.nntp/c/p4NgdFEMeIU>
>
> As I see it, the problem can only be solved in this order:
> 1. Google (who is nearly impossible to communicate with)
> 2. Peers (like highwinds, the assholes that they are)
> 3. Users
>
> Starting in order...
>
> I have had success with getting Google to fix Maps (but they care about
> that product) but since I happen to live relatively near Mountainview,
> maybe I can pay them a visit?
>
> Do those groups you speak of have a _contact_ at Google I can try to reach?

No. One of the persons in those groups worked for Google, but even he
has given up trying to get Google to respond/act.

See my other response (to Carlos and indirectly to you) for what the
News admins are doing and how.

On 2023-12-04 16:45, Frank Slootweg wrote:
> Carlos E. R. <robin_listas@es.invalid> wrote:
>> On 2023-12-04 08:57, Wally J wrote:
>>> Wally J <walterjones@invalid.nospam> wrote
>>>
>>>> As I see it, the problem can only be solved in this order:
>>>> 1. Google (who is nearly impossible to communicate with)
>>>> 2. Peers (like highwinds, the assholes that they are)
>>>> 3. Users
>>>
>>> I had a long conversation with the folks on the nntp & peering ngs.
>>> They say Google doesn't care. Nor do the peers like Highwinds & Giganews.
>>> So it may be up to each of us.
>>>
>>> But that's crazy.
>>> One person should write the filter (who knows the tool inside & out).
>>> And the rest of the people should just copy it and use it.
>
> The News admins of the well-managed servers already made tools and are
> sharing them amongst themselves. The main method used is NoCeM (No See
> 'Em).
>
> 'The NoCeM FAQ'
> <http://www.cm.org/faq.html>
>
>>> Here's a web site trying to do something about it to help users implement
>>> the filter since it's best if one person implements it & the others copy.
>>> <http://twovoyagers.com/improve-usenet.org/index.html>
>>
>> Filtering out all of Google Groups locally is trivial.
>>
>> Just delete mail or delete subthreads (your choice) when
>> User-Agent is "G2/1.0".
>
> Exactly. While the News admins are trying to do their bit, we users
> can do our bit, by filtering any remaining Google Groups posts and - if
> wanted - whitelisting the good (GG) guys.
>
>> Filtering only the spam is hard: clients like Thunderbird lack spam
>> filters on the nntp side. You can do filters to remove spam that matches
>> some pattern, but not changing patterns.
>>
>> Servers like News.Individual.NET are filtering out the Google spam (or
>> most of it), with a small delay, so moving to those servers is other
>> thing that users can do.
>
> AFAIK, News.Individual.NET uses the above mentioned NoCeM method.

I will read about it later, but now I'm going for my siesta.
There is a caveat with Thunderbird:

There is a delay till News.Individual.NET deletes the google spam, and
often some spam is read by Thunderbird and displays. Sometime later, on
clicking on some other spam post, Thunderbird says that the post can not
be downloaded because it was expired, and offers to purge all expired
posts in the current group.

Also, this may have an effect on my desktop machine, where News are
downloaded by fetchnews to a local cache, and I have no idea if
deletions upstream will propagate.

>
>> But IMO, the best thing to do would be to disconnect Usenet servers from
>> Google, so that Google can not send nor receive from Usenet. That might
>> force them to investigate and talk. Might. If they don't, who cares.
>
> Sofar, the consensus amongst the News admins is that they care enough
> about the legit Google Groups posters to continue filtering the (GG
> originated) spam from their servers.

I can understand that.

--
Cheers,
Carlos E.R.

Carlos E. R. <robin_listas@es.invalid> wrote:
> On 2023-12-04 16:45, Frank Slootweg wrote:
[...]
> > The News admins of the well-managed servers already made tools and are
> > sharing them amongst themselves. The main method used is NoCeM (No See
> > 'Em).
> >
> > 'The NoCeM FAQ'
> > <http://www.cm.org/faq.html>
[...]
> > AFAIK, News.Individual.NET uses the above mentioned NoCeM method.
>
> I will read about it later, but now I'm going for my siesta.
> There is a caveat with Thunderbird:
>
> There is a delay till News.Individual.NET deletes the google spam, and
> often some spam is read by Thunderbird and displays. Sometime later, on
> clicking on some other spam post, Thunderbird says that the post can not
> be downloaded because it was expired, and offers to purge all expired
> posts in the current group.
>
>
> Also, this may have an effect on my desktop machine, where News are
> downloaded by fetchnews to a local cache, and I have no idea if
> deletions upstream will propagate.

I use tin as my newsreader and Hamster as my local 'cache' and do not
have this problem. But Hamster is a real news-server, so probably
Hamster hides the NIN expiration issue from tin.

I guess you could install WINE and Hamster on top of that! :-)

But seriously: What local cache do you use? Leafnode[2]? slrnpull?
Other?

[...]

On 03.12.23 17:37, bad sector wrote:
> On 12/3/23 10:59 AM, Jörg Lorenz wrote:
>> Am 03.12.23 um 16:12 schrieb bad sector:
>>>
>>>
>>> I see this NG is also being attacked by spammers,
>>> I guess google really wants to muzzle it.
>>
>> Here it is absolutely spamfree.
>>
>> Your client - albeit so old it already turned to dust - would easily
>> allow you to filter it. Or use Solani, E-S or individual.net.
>
> Sticking one's head in the sand doesn't impede google,
> and no one else is behind all the spam as far as I'm
> concerned because no one else wants to destroy usenet
> as much as google does. The prime beneficiary has to
> be the prime suspect. The same problem on many, many
> other NG's and no one is going to convince me that
> spammers would be so attracted by a dying platform.

Pure conspiracy theory.

--
"Gutta cavat lapidem." (Ovid)

Frank Slootweg <this@ddress.is.invalid> wrote

>> Do those groups you speak of have a _contact_ at Google I can try to reach?
>
> No. One of the persons in those groups worked for Google, but even he
> has given up trying to get Google to respond/act.

Thanks. And yes, I communicated with Grant Taylor who used to work at
Google. I have a few friends also who retired early due to Google. At the
moment, everyone I knew well stopped working at Google though. So I only
have their main contact number, and nothing better than a local call.

Grant suggested (and I quote) "If you want to get an individual person to
rattle Google's cage, try to get someone like Tavis Ormandy of Google's
Project Zero" so I will give them a call today, but I won't hold my breath.

The only three things I've ever had even a teeny tiny bit of success with
Google on a personal level is Rod Speed's murder email, changing Usenet
URIs to the dejagoogle archives and fixing local Google Maps routing.

> See my other response (to Carlos and indirectly to you) for what the
> News admins are doing and how.

Yeah, I saw that. I see everything you post to this newsgroup, Frank. So
you can assume if you posted it, I'll see it. I like what they're doing.

The spam on the Android newsgroup has made it unusable without filtering.
<https://i.postimg.cc/6pj29c6f/spam01.jpg>

So I appreciate that you opened this thread, and posted good info like
'The NoCeM FAQ' <http://www.cm.org/faq.html>

On the web there is this URL that says it allows you to
"Contact Owners and Managers of Google Usenet"
*Google Usenet* (google-usenet@googlegroups.com)
<https://groups.google.com/g/google-usenet/about>

There is a settings-gear-icon image at top right, which has the option to:
"Send feedback to Google"
1. Tell us what prompted this feedback.
2. A screenshot will help us better understand your feedback.

Here's a screenshot of that which I recommend others do right now.
<https://i.postimg.cc/k462x02X/spam02.jpg>

In addition, there's this generic "starting point" phone number:
<https://about.google/intl/ALL_us/contact-google/>
650-253-0000 (googleplex automated human)
Which only works "Monday to Friday from 8 am to 5 pm PST".
You're saying "It's something else" a few times.
Then you "Continue to hold for the next available Agent" human.

While I was waiting, I went to see if there's a contact on Wikipedia.
<https://en.wikipedia.org/wiki/Google_Groups>
Nothing useful there except the DejaNews history we already know.

Still waiting, I looked up "how to contact google for real"
<https://www.businessinsider.com/guides/tech/how-to-contact-google-support>
But they only said what I knew e.g., "Google doesn't want to talk to you".

Still waiting... I searched s'more and found other garbage such as this.
<https://groups.google.com/g/google-usenet>
Or this "chat support" link:
<https://support.google.com/chatsupport/?hl=en>
But all it has is a single article on "Add a Google Group to a space".

Still waiting...

On 2023-12-04 17:25, Frank Slootweg wrote:
> Carlos E. R. <robin_listas@es.invalid> wrote:
>> On 2023-12-04 16:45, Frank Slootweg wrote:
> [...]
>>> The News admins of the well-managed servers already made tools and are
>>> sharing them amongst themselves. The main method used is NoCeM (No See
>>> 'Em).
>>>
>>> 'The NoCeM FAQ'
>>> <http://www.cm.org/faq.html>
> [...]
>>> AFAIK, News.Individual.NET uses the above mentioned NoCeM method.
>>
>> I will read about it later, but now I'm going for my siesta.
>> There is a caveat with Thunderbird:
>>
>> There is a delay till News.Individual.NET deletes the google spam, and
>> often some spam is read by Thunderbird and displays. Sometime later, on
>> clicking on some other spam post, Thunderbird says that the post can not
>> be downloaded because it was expired, and offers to purge all expired
>> posts in the current group.
>>
>>
>> Also, this may have an effect on my desktop machine, where News are
>> downloaded by fetchnews to a local cache, and I have no idea if
>> deletions upstream will propagate.
>
> I use tin as my newsreader and Hamster as my local 'cache' and do not
> have this problem. But Hamster is a real news-server, so probably
> Hamster hides the NIN expiration issue from tin.
>
> I guess you could install WINE and Hamster on top of that! :-)
>
> But seriously: What local cache do you use? Leafnode[2]? slrnpull?
> Other?

Leafnode, the development version.

--
Cheers,
Carlos E.R.