[Dialog] Filter needed to get rid of Google Groups spam by Message-ID or by User-Agent
A lot of newsgroups are being spammed lately from Google Groups.
When I "Rightclick -> Scoring & actions -> Add plonk rule" on a message in 40tude dialog, it only catches the "From:" but not the message-id which,
for google groups messages ends with "@googlegroups.com"
What's the way to get a filter based on the googlegroups message id?
I noticed they also come from "User-Agent: G2/1.0" so that would work too.
I noticed they also come from "User-Agent: G2/1.0" so that would work too.
If possible, the best way is the Injection-Info which contains : google-groups.googlegroups.com
But the User-Agent G2/1.0 seems to be only used by google-groups...
A lot of newsgroups are being spammed lately from Google Groups.
When I "Rightclick -> Scoring & actions -> Add plonk rule" on a message in 40tude dialog, it only catches the "From:" but not the message-id which,
for google groups messages ends with "@googlegroups.com"
What's the way to get a filter based on the googlegroups message id?
I noticed they also come from "User-Agent: G2/1.0" so that would work too.
If possible, the best way is the Injection-Info which contains : google-groups.googlegroups.com
But the User-Agent G2/1.0 seems to be only used by google-groups...
If possible, the best way is the Injection-Info which contains : google-groups.googlegroups.com
But the User-Agent G2/1.0 seems to be only used by google-groups...
[news.software.readers]
!markread,ignore Header {^(Injection-Info: [^.]*.googlegroups.com;posting-host=[0-9.]*; posting-account=)}
This could be done this way in 40tude Dialog:
!markread,ignore Header {^(Injection-Info: [^.]*.googlegroups.com; posting-host=[0-9.]*; posting-account=)}
By filling out the posting-account in the above example, this filter can be adjusted to a single Googlegroups user.
But the User-Agent G2/1.0 seems to be only used by google-groups...
!move(SPAM) Header "User-Agent: G2/1.0"
This example shows another filter method for 40tude Dialog. It would move fetched messages into a (prior created) SPAM folder. This way, any false positive would stay accessible, if need be.
Bernd
I created a folder in the same directory as dialog.exe was in.
mkdir SPAM
I added this to Dialog's "Settings | Scoring & actions" & pressed OK.
[comp.mobile.android]
!move(SPAM) Header "User-Agent: G2/1.0"
Then I opened up to that newsgroup and the SPAM folder was empty.
But spam of the Google Groups type came in so I need to do something more. But what?
Can this be used to whitelist people?
[news.software.readers]
!markread,ignore Header {^(Injection-Info: [^.]*.googlegroups.com;posting-host=[0-9.]*; posting-account=)}
If the posting account is in the whitelist, let them through.
Otherwise plonk them.
[...]-10 From gmail.com +@Message-ID: googlegroups.com
+100 Header {^(Injection-Info: .*; posting-account=1234abcd)}
+100 Header {^(Injection-Info: .*; posting-account=9876zyxw)}
!move(SPAM) Score %<0
There is a basic flaw here: the use of a From: *@gmail address does not necessarily indicate a Google Groups poster. I myself use such an
adddress but I post via Eternal-September. If you killfile on From: in
that way you will get many false positives. IMO it's better to k/f on
Path; Message-ID; Injection-Info; or User-Agent (which last I use successfully).
This post is probably futile as I expect that Bernd has me killfiled by
From: address and will not see it.
Bernd Rose <b.rose.tmpbox@arcor.de> wrote:
On Sun, 3rd Dec 2023 21:38:12 -0500, rocco portelli wrote:[^.]*.googlegroups.com;posting-host=[0-9.]*; posting-account=)}
Can this be used to whitelist people?
[news.software.readers]
!markread,ignore Header {^(Injection-Info:
[^.]*.googlegroups.com; posting-host=[0-9.]*; posting-account=1234abcd)}
If the posting account is in the whitelist, let them through.
Otherwise plonk them.
There are several possible approaches to this matter. They will fail
the most important point, though, as long as they are based on
Injection-Info,
because this requires the body to be loaded...
A few pointers:
This example will move any message from gmail.com if it has not the
injection info for poster 1234abcd:
!move(SPAM) From gmail.com -@Header: {^(Injection-Info:
It will only work for one (or very few) whitelist entries, though. With
a larger whitelist, it would be better to use scoring first:
-10 From gmail.com +@Message-ID: googlegroups.com +100 Header
{^(Injection-Info: .*; posting-account=1234abcd)}
+100 Header {^(Injection-Info: .*; posting-account=9876zyxw)}
!move(SPAM) Score %<0
To use this without loading the bodies, you'd need to find a different
method to identify whitelist posters. (Not injection info, because it
is not part of the basic Overview headers, as I already wrote...)
Bernd
There is a basic flaw here: the use of a From: *@gmail address does not necessarily indicate a Google Groups poster. I myself use such an
adddress but I post via Eternal-September. If you killfile on From: in
that way you will get many false positives. IMO it's better to k/f on
Path; Message-ID; Injection-Info; or User-Agent (which last I use successfully).
This post is probably futile as I expect that Bernd has me killfiled by
From: address and will not see it. Perhaps some kind reader might
followup to this article so he can see it. TIA
This post is probably futile as I expect that Bernd has me killfiled by
From: address and will not see it.
Apart from the fact, that above filter wouldn't be triggered by your
message, anyway: I don't use that filter, myself. It is just an example
for a possible filter method, that /might/ fit the needs of the OP.
On Mon, 4th Dec 2023 23:03:51 +0000, Sn!pe wrote:
[...]-10 From gmail.com +@Message-ID: googlegroups.com
+100 Header {^(Injection-Info: .*; posting-account=1234abcd)}
+100 Header {^(Injection-Info: .*; posting-account=9876zyxw)}
!move(SPAM) Score %<0
There is a basic flaw here: the use of a From: *@gmail address does not necessarily indicate a Google Groups poster. I myself use such an
adddress but I post via Eternal-September. If you killfile on From: in that way you will get many false positives. IMO it's better to k/f on Path; Message-ID; Injection-Info; or User-Agent (which last I use successfully).
The filter above only triggers when From is "gmail.com" AND (+@)
Message-Id is "googlegroups.com".
Alas, my antediluvian News reader doesn't offer filtration on M-ID or Injection-Info so I must rely on Path or User-Agent. The latter works
well for me and has the effect of a 'mark as read' rule so that it's
easy to backspace up the thread to read it if appropriate.
Bear in mind that I'm a humble luser who lacks the skills to hack what
is otherwise my perfect News reader in the cause of expanding its
filtration capability.
In the past, Stefan Haller (the author of MacSOUP) has been kind enough
to implement a couple of my suggestions. Alas, since MacOS went 64-bit, MacSOUP will no longer run and Stefan has understandably decided not
rewrite it, so it's abandonware. I'm wedded to MacSOUP so I keep a
legacy machine going for the sole purpose of running it.
Hamster has Dialog-like and largely Dialog-compatible scoring/filtering.
[...]-10 From gmail.com +@Message-ID: googlegroups.com
The filter above only triggers when From is "gmail.com" AND (+@)
Message-Id is "googlegroups.com".
A user might want to filter on only Message-Id is "googlegroups.com", because AFAIK one can use a non-gmail.com address to post from Google
Groups. While such a combination is probably not common, it is (AFAIK) possible.
On 5th Dec 2023 14:17:03 GMT, Frank Slootweg wrote:
Hamster has Dialog-like and largely Dialog-compatible scoring/filtering.
Actually, it is the other way round: Hamster predates Dialog. The author
of 40tude Dialog (Marcus Moennig) explicitly based the scoring/filtering system on the one introduced with Hamster. ;-)
Do I know you by a different name, perhaps in another place, Oscar?
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 483 |
Nodes: | 16 (1 / 15) |
Uptime: | 80:51:51 |
Calls: | 9,576 |
Calls today: | 7 |
Files: | 13,666 |
Messages: | 6,142,985 |
Posted today: | 2 |