I think I (just, but only just) preferred Holmans' pro-English bullshit rather than the weird stuff infecting this group nowadays.

On 10/3/2023 8:47 AM, Tony The Welsh Twat wrote:
> I think I (just, but only just) preferred Holmans' pro-English bullshit rather than the weird stuff infecting this group nowadays.

VERY EASY to INTIMIDATE the filthy cross dressing, lipstick wearing,
confused gender EVIL US GOVT WHITE CIA NSA FBI DHS cowards and pussies.

IF you ask them to come out and FIGHT their opponents with exactly the
SAME/EQUAL WEAPONS, the whitefucks will RUN like hell, HIDE behind their
WHORE MOMMIES and CRY I don't wanna die, I don't wanna die, I don't
wanna die, pleas don't kill me, please don't kill me, please don't kill me.

POC have been too nice and too tolerant to the EVIL US Govt psychopathic
BLOOD THIRSTY THIEVES for too long.

IF Native americans MERCILESSLY MASSACRED the EVIL EUROPEAN THIEVES ON
SIGHT, america would still be owned by Native Red Indians instead of the
EVIL WHITE THIEVES.

It's actually NOT TOO LATE for POC to massacre the WHITE THIEVES like
pigs and SAVE their LAND, WEALTH and DIGNITY.

Niger kicked out european THIEVES recently but it is NOT over yet. The
CUNNING WHITE THIEVES will go back and do a SNEAK ATTACK and REPLACE the
Govt with PUPPETS to STEAL their NATURAL RESOURCES.

The WHOLE WORLD MUST "PERCEIVE" western whites as a RACE OF BLOODTHIRSTY
THIEVES and MASSACRE them ON SIGHT. They have the SELF DEFENSE RIGHT to
PROTECT THEMSELVES, their women and children, their WEALTH and LAND.

A WHITE MAN is an OXYMORON - Whites are a RACE of fucking COWARDS n PUSSIES
https://groups.google.com/g/misc.survivalism/c/5YYq6QlQ0PI/m/cb_SR32SAAAJ

A WHITE MAN is an OXYMORON - Whites are a RACE of fucking COWARDS n PUSSIES

At the current rate of western white men coming out as gays, trans and the
other 100+ confused genders Western Whites CREATED out of their
PERVERSIONS and DECADENCE, there WON'T be a straight white man left in a
couple of decades.

WESTERN WHITE CHRISTIANS HAVE ALWAYS BEEN A RACE OF PUSSIES and COWARDS
their entire existence.

But the american whites "cunningly programmed" everybody to THINK that
America is "home of the brave".

The proof is in the pudding.

1) You ask a white man to fight their opponents with "exactly the same
weapons" and you will see whites "wetting their panties" and running and
hiding behind their whore moms and cry "I don't wanna die, please don't
kill me".

2) White Christian America DID NOT HAVE THE BALLS to fight Japan in
conventional war which is why they "NUKED Japan TWICE".

3) RACIST White Christian America DID NOT NUKE Germany even once",
"because GERMANS are WHITE CHRISTIANS."

4) White Christian America DID NOT HAVE THE BALLS to fight a war with
RUSSIA because RUSSIA HAD NUKES.

5) White Christian America with SUPERIOR WEAPONS fights wars ONLY with
"PUNY POWERLESS COUNTRIES" like Iraq, Somalia, Granada, Yugoslavia, Libya
Afghanistan who don't have nukes and don't have good enough weapons to
fight USA.

6) White Christian America does NOT HAVE THE BALLS to Fight China in a
war because CHINA HAS NUKES.

7) If you offer a hand of friendship, bible thumping whites will smile,
shake hands and BACKSTAB YOU when you turn back, KILL you and STEAL your
wealth and land.

8) On the other hand, if YOU PUT A GUN to a White man's head, "it" will
"WET ITS -PANTIES- AND BEG YOU FOR MERCY".

9) Western White Women are BREEDING a RACE of COWARD FILTHY EVIL VIRUS and
DESTROYING the beautiful planet and human species.

10) FACT:

USA "never fought a war" with ANY country with "equal weapons or nukes"
in its "ENTIRE EXISTENCE", because USA is a "Nation of COWARDS and
PUSSIES".

11) WHITES FEAR "DEATH" like NO OTHER RACE on the planet.

12) Whites were NEVER BRAVE in reality, it is just a "PERCEPTION created
in their minds and the rest of the humans' minds by the INFINITELY
CUNNING DECEPTIVE whites".

On 10/3/2023 8:47 AM, Tony The Welsh Twat wrote:
> I think I (just, but only just) preferred Holmans' pro-English bullshit rather than the weird stuff infecting this group nowadays.

You are a fucking typical WHITE COWARD and a PUSSY who will WET and SHIT
YOUR PANTIES if asked to fight their opponent with exactly the
same/equal weapon

Western White Women are BREEDING a "filthy COWARD PSYCHOPATHIC VIRUS".

The SOONER the rest of the world join hands, INVADE the FILTHY EVIL
WHITE VIRUS and FORCIBLY SUBJUGATE, REFORM, HUMANIZE and CIVILIZE the
EVIL bloodthirsty genocidal sadistic perverted pedophilic bestial
cannibalistic Western White Race, the BETTER for the world and the UNIVERSE.

The WORLD has put up with the EVIL WHITE VIRUS for too long.

In message <5a16898a-1e5c-43f8-8d6c-7216962d8b02n@googlegroups.com>,
Tony The Welsh Twat <tonythewelshtwat@gmail.com> writes
>I think I (just, but only just) preferred Holmans' pro-English bullshit
>rather than the weird stuff infecting this group nowadays.

It marks it hard to find the wheat among the chaff, doesn't ?
uk.sci.weather has been similarly inflicted. If you have a newsreader
that offers killfiling facilities which allow so-called "regular
expressions", then the custom reject rule

/^Content\-Transfer\-Encoding..base64$/h

should get rid of any future instances without causing any collateral
damage.
--
John Hall "[It was] so steep that at intervals the street broke into steps,
like a person breaking into giggles or hiccups, and then resumed
its sober climb, until it had another fit of steps."
Ursula K Le Guin "The Beginning Place"

In message <Uep8vUCxpEHlFw0q@jhall_nospamxx.co.uk>, John Hall
<john_nospam@jhall.co.uk> writes
>It marks it hard to find the wheat among the chaff, doesn't ?
>uk.sci.weather has been similarly inflicted. If you have a newsreader
>that offers killfiling facilities which allow so-called "regular
>expressions", then the custom reject rule
>
>/^Content\-Transfer\-Encoding..base64$/h
>
>should get rid of any future instances without causing any collateral
>damage.

Thanks, I've just tried that in Turnpike (as a custom rule), but the
torrent continues.

Adrian
--
To Reply :
replace "bulleid" with "adrian" - all mail to bulleid is rejected
Sorry for the rigmarole, If I want spam, I'll go to the shops
Every time someone says "I don't believe in trolls", another one dies.

On Tue, 3 Oct 2023 19:41:00 +0100, Adrian <bulleid@ku.gro.lioff>
wrote:

>In message <Uep8vUCxpEHlFw0q@jhall_nospamxx.co.uk>, John Hall
><john_nospam@jhall.co.uk> writes
>>It marks it hard to find the wheat among the chaff, doesn't ?
>>uk.sci.weather has been similarly inflicted. If you have a newsreader
>>that offers killfiling facilities which allow so-called "regular
>>expressions", then the custom reject rule
>>
>>/^Content\-Transfer\-Encoding..base64$/h
>>
>>should get rid of any future instances without causing any collateral
>>damage.
>
>Thanks, I've just tried that in Turnpike (as a custom rule), but the
>torrent continues.
>
>Adrian
>
I used it just there in Forte and it filtered a load, still a few
resisting.

max.it

In message <74BlDSU8AGHlFwy3@ku.gro.lloiff>, Adrian
<bulleid@ku.gro.lioff> writes
>In message <Uep8vUCxpEHlFw0q@jhall_nospamxx.co.uk>, John Hall
><john_nospam@jhall.co.uk> writes
>>It marks it hard to find the wheat among the chaff, doesn't ?
>>uk.sci.weather has been similarly inflicted. If you have a newsreader
>>that offers killfiling facilities which allow so-called "regular
>>expressions", then the custom reject rule
>>
>>/^Content\-Transfer\-Encoding..base64$/h
>>
>>should get rid of any future instances without causing any collateral
>>damage.
>
>Thanks, I've just tried that in Turnpike (as a custom rule), but the
>torrent continues.
>
>Adrian

I'm using TP too, so it should have worked for you. Did you set the rule
in the correct place, by right-clicking on the name of the newsgroup and
then selecting Properties and going from there? And did you remember to
click on the Reject radio button?

Could you post the headers from one of the spam articles? I'm wondering
if the ones that my rule works against have stopped comi9ng and you're
getting different ones that some older kill rule of mine happens to
stop.
--
John Hall "[It was] so steep that at intervals the street broke into steps,
like a person breaking into giggles or hiccups, and then resumed
its sober climb, until it had another fit of steps."
Ursula K Le Guin "The Beginning Place"

In message <i9HBHfDLNHHlFwB8@jhall_nospamxx.co.uk>, John Hall
<john_nospam@jhall.co.uk> writes
>In message <74BlDSU8AGHlFwy3@ku.gro.lloiff>, Adrian
><bulleid@ku.gro.lioff> writes
>>In message <Uep8vUCxpEHlFw0q@jhall_nospamxx.co.uk>, John Hall
>><john_nospam@jhall.co.uk> writes
>>>It marks it hard to find the wheat among the chaff, doesn't ?
>>>uk.sci.weather has been similarly inflicted. If you have a newsreader
>>>that offers killfiling facilities which allow so-called "regular
>>>expressions", then the custom reject rule
>>>
>>>/^Content\-Transfer\-Encoding..base64$/h
>>>
>>>should get rid of any future instances without causing any collateral
>>>damage.
>>
>>Thanks, I've just tried that in Turnpike (as a custom rule), but the torrent
>>continues.
>>
>>Adrian
>
>I'm using TP too, so it should have worked for you. Did you set the rule in
>the correct place, by right-clicking on the name of the newsgroup and
>then selecting Properties and going from there? And did you remember to
>click on the Reject radio button?
>

I've just double checked, it is for the right group, it is a custom
rule, and it is set to reject. The rule was cut and pasted from your
previous posting.

>Could you post the headers from one of the spam articles? I'm wondering
>if the ones that my rule works against have stopped comi9ng and you're
>getting different ones that some older kill rule of mine happens to stop.

From the latest batch :

X-Received: by 2002:a05:622a:1742:b0:417:b90d:2d4 with SMTP id
l2-20020a05622a174200b00417b90d02d4mr5006qtk.5.1696362001427;
Tue, 03 Oct 2023 12:40:01 -0700 (PDT)
X-Received: by 2002:a05:6808:1b0c:b0:3a7:86b2:1950 with SMTP id
bx12-20020a0568081b0c00b003a786b21950mr310403oib.0.1696362001084; Tue,
03 Oct
2023 12:40:01 -0700 (PDT)
Path:
eternal-september.org!news.eternal-september.org!fu-berlin.de!news-out.go
ogle.com!nntp.google.com!postnews.google.com!google-groups.googlegroups.c
om!not-for-mail
Newsgroups: uk.sport.cricket
Date: Tue, 3 Oct 2023 12:40:00 -0700 (PDT)
Injection-Info: google-groups.googlegroups.com;
posting-host=2a0e:a942:8c03:6220:2751:2fbc:bcde:d79b;
posting-account=knYgnwoAAAAxY1xrjIdINnEz3h8xcl_W
NNTP-Posting-Host: 2a0e:a942:8c03:6220:2751:2fbc:bcde:d79b
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <ebd9df29-2a31-426c-9c40-83c1f8e89dc7n@googlegroups.com>
Subject:
=?UTF-8?B?8J+SjiBVRkFYMiDguYDguILguYnguLLguKrguLnguYjguKPguLDguJrguJotIOC
4hOC4sg==?=
=?UTF-8?B?4Liq4Li04LmC4LiZ4Lit4Lit4LiZ4LmE4Lil4LiZ4LmM4LmB4Lil4Li
w4LmA4Lin4LmH4Lia4Lie4LiZ?=
=?UTF-8?B?4Lix4LiZ4Lit4Lix4LiZ4LiU4Lix4Lia4Lir4LiZ4Li24LmI4LiH4Lm
D4LiZ4Lib4Lij4Liw4LmA4LiX?=
=?UTF-8?B?4Lio4LmE4LiX4LiiIPCfko4gdWZhMXgyIOC5gOC4guC5ieC4suC4quC
4ueC5iOC4o+C4sOC4muC4miA=?=
From:
=?UTF-8?B?4LmC4Lif4LiB4Lix4LiqIOC4p+C4seC4iuC4o+C4iOC4tOC4o+C4sOC4geC4uOC
4pQ==?= <zuelligmancharonemb@gmail.com>
Injection-Date: Tue, 03 Oct 2023 19:40:01 +0000
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: base64
Xref: news.eternal-september.org uk.sport.cricket:116396

Adrian
--
To Reply :
replace "bulleid" with "adrian" - all mail to bulleid is rejected
Sorry for the rigmarole, If I want spam, I'll go to the shops
Every time someone says "I don't believe in trolls", another one dies.

In message <upQwXKX5jHHlFwBV@ku.gro.lloiff>, Adrian
<bulleid@ku.gro.lioff> writes
>In message <i9HBHfDLNHHlFwB8@jhall_nospamxx.co.uk>, John Hall
><john_nospam@jhall.co.uk> writes
>>In message <74BlDSU8AGHlFwy3@ku.gro.lloiff>, Adrian
>><bulleid@ku.gro.lioff> writes
>>>In message <Uep8vUCxpEHlFw0q@jhall_nospamxx.co.uk>, John Hall
>>><john_nospam@jhall.co.uk> writes
>>>>It marks it hard to find the wheat among the chaff, doesn't ?
>>>>uk.sci.weather has been similarly inflicted. If you have a newsreader
>>>>that offers killfiling facilities which allow so-called "regular
>>>>expressions", then the custom reject rule
>>>>
>>>>/^Content\-Transfer\-Encoding..base64$/h
>>>>
>>>>should get rid of any future instances without causing any collateral
>>>>damage.
>>>
>>>Thanks, I've just tried that in Turnpike (as a custom rule), but the torrent
>>>continues.
>>>
>>>Adrian
>>
>>I'm using TP too, so it should have worked for you. Did you set the rule in
>>the correct place, by right-clicking on the name of the newsgroup and
>>then selecting Properties and going from there? And did you remember to
>>click on the Reject radio button?
>>
>
>I've just double checked, it is for the right group, it is a custom
>rule, and it is set to reject. The rule was cut and pasted from your
>previous posting.
>
>
>>Could you post the headers from one of the spam articles? I'm wondering
>>if the ones that my rule works against have stopped comi9ng and you're
>>getting different ones that some older kill rule of mine happens to stop.
>
>From the latest batch :
>
<snip>
>Content-Transfer-Encoding: base64
>Xref: news.eternal-september.org uk.sport.cricket:116396

It's the same as I was getting, so the rule should have worked. The ^
ties the rule to the start of the line, the \ is the "escape" character
so that the following - is taken literally rather than as a control
character, the .. says match any two characters (because I couldn't
recall if the : or the space needed to be escaped or not, the $ ties it
to the end of the line, and the final h says check all header lines for
a match. You could try simplifying the rule to

/base64/h

which AIUI should check for that string in any position within the line
- less efficient in terms of processing time, but there's less to go
wrong.

The only possible explanation I can think of is that you're using a
different news server to me, and to wonder if it's somehow mangling the
headers in some way invisible to the naked eye - which it shouldn't do,
of course. For instance, if it added a space character to the end of
each header, that would mean that the $ at the end of my original rule
would prevent a match.
--
John Hall "[It was] so steep that at intervals the street broke into steps,
like a person breaking into giggles or hiccups, and then resumed
its sober climb, until it had another fit of steps."
Ursula K Le Guin "The Beginning Place"

In message <eDCuYeEcBIHlFw1M@jhall_nospamxx.co.uk>, John Hall
<john_nospam@jhall.co.uk> writes
>In message <upQwXKX5jHHlFwBV@ku.gro.lloiff>, Adrian
><bulleid@ku.gro.lioff> writes
>>In message <i9HBHfDLNHHlFwB8@jhall_nospamxx.co.uk>, John Hall
>><john_nospam@jhall.co.uk> writes
>>>In message <74BlDSU8AGHlFwy3@ku.gro.lloiff>, Adrian
>>><bulleid@ku.gro.lioff> writes
>>>>In message <Uep8vUCxpEHlFw0q@jhall_nospamxx.co.uk>, John Hall
>>>><john_nospam@jhall.co.uk> writes
>>>>>It marks it hard to find the wheat among the chaff, doesn't ?
>>>>>uk.sci.weather has been similarly inflicted. If you have a newsreader
>>>>>that offers killfiling facilities which allow so-called "regular
>>>>>expressions", then the custom reject rule
>>>>>
>>>>>/^Content\-Transfer\-Encoding..base64$/h
>>>>>
>>>>>should get rid of any future instances without causing any collateral
>>>>>damage.
>>>>
>>>>Thanks, I've just tried that in Turnpike (as a custom rule), but the torrent
>>>>continues.
>>>>
>>>>Adrian
>>>
>>>I'm using TP too, so it should have worked for you. Did you set the rule in
>>>the correct place, by right-clicking on the name of the newsgroup and
>>>then selecting Properties and going from there? And did you remember to
>>>click on the Reject radio button?
>>>
>>
>>I've just double checked, it is for the right group, it is a custom
>>rule, and it is set to reject. The rule was cut and pasted from your
>>previous posting.
>>
>>
>>>Could you post the headers from one of the spam articles? I'm wondering
>>>if the ones that my rule works against have stopped comi9ng and you're
>>>getting different ones that some older kill rule of mine happens to stop.
>>
>>From the latest batch :
>>
><snip>
>>Content-Transfer-Encoding: base64
>>Xref: news.eternal-september.org uk.sport.cricket:116396
>
>It's the same as I was getting, so the rule should have worked. The ^
>ties the rule to the start of the line, the \ is the "escape" character
>so that the following - is taken literally rather than as a control
>character, the .. says match any two characters (because I couldn't
>recall if the : or the space needed to be escaped or not, the $ ties it
>to the end of the line, and the final h says check all header lines for
>a match. You could try simplifying the rule to
>
>/base64/h
>
>which AIUI should check for that string in any position within the line
>- less efficient in terms of processing time, but there's less to go
>wrong.
>
>The only possible explanation I can think of is that you're using a
>different news server to me, and to wonder if it's somehow mangling the
>headers in some way invisible to the naked eye - which it shouldn't do,
>of course. For instance, if it added a space character to the end of
>each header, that would mean that the $ at the end of my original rule
>would prevent a match.

Thanks.

I've added another custom rule to reject /base64/h, I'll see what
happens.

I'm using Eternal September as my news server.

Adrian
--
To Reply :
replace "bulleid" with "adrian" - all mail to bulleid is rejected
Sorry for the rigmarole, If I want spam, I'll go to the shops
Every time someone says "I don't believe in trolls", another one dies.

In message <hFtzMtYPVIHlFwzx@ku.gro.lloiff>, Adrian
<bulleid@ku.gro.lioff> writes
>I've added another custom rule to reject /base64/h, I'll see what
>happens.
>

That doesn't seem to have worked either.

Adrian
--
To Reply :
replace "bulleid" with "adrian" - all mail to bulleid is rejected
Sorry for the rigmarole, If I want spam, I'll go to the shops
Every time someone says "I don't believe in trolls", another one dies.

On 03/10/2023 23:50, Adrian wrote:
>> I've added another custom rule to reject /base64/h, I'll see what happens.
> That doesn't seem to have worked either.

I've tried various strings from the Subject [such as "ufa" and
"UTF-8"] and Injection-Info ["2a0e:a942"], some of which gave partial
success, but TB seems to miss these quite often even when they're
staring it in the face. I'm sorry to report that the only 100% [so far]
success I've had has been by rejecting messages from Gmail. I suspect
that will also catch some genuine posters [inc Tony, the OP].

--
Andy Walker, Nottingham.
Andy's music pages: www.cuboid.me.uk/andy/Music
Composer of the day: www.cuboid.me.uk/andy/Music/Composers/Henselt

In message <ufj9cj$2qai$1@dont-email.me>, Andy Walker <anw@cuboid.co.uk>
writes
>On 03/10/2023 23:50, Adrian wrote:
>>> I've added another custom rule to reject /base64/h, I'll see what happens.
>> That doesn't seem to have worked either.
>
> I've tried various strings from the Subject [such as "ufa" and
>"UTF-8"] and Injection-Info ["2a0e:a942"], some of which gave partial
>success, but TB seems to miss these quite often even when they're
>staring it in the face. I'm sorry to report that the only 100% [so far]
>success I've had has been by rejecting messages from Gmail. I suspect
>that will also catch some genuine posters [inc Tony, the OP].
>

You could both try "=?UTF" for the subject, which I had some success
with before trying the "base64" rule. (Since it's not a custom rule, the
= and ? aren't control characters but are taken literally.) It might not
work with Thunderbird if it's modern enough to know that =?UTF-8? is
control info rather than supposed to be taken literally, though.

I use news.individual.net, which is normally very good at filtering out
spam, but the encoding of these messages seems to have defeated it.
There are so many, and they are so hard to read, that I wonder if they
are intended as a denial of service attack rather than spam. Either way,
the creator seems to have gone to an awful lot of trouble. For some
reason, so far of the groups I take only this group and uk.sci.weather
have been affected. It's not even all uk.* groups, as others I take have
so far been clear.
--
John Hall "[It was] so steep that at intervals the street broke into steps,
like a person breaking into giggles or hiccups, and then resumed
its sober climb, until it had another fit of steps."
Ursula K Le Guin "The Beginning Place"

On Wednesday, 4 October 2023 at 09:56:54 UTC+1, Andy Walker wrote:
> On 03/10/2023 23:50, Adrian wrote:
> >> I've added another custom rule to reject /base64/h, I'll see what happens.
> > That doesn't seem to have worked either.
> I've tried various strings from the Subject [such as "ufa" and
> "UTF-8"] and Injection-Info ["2a0e:a942"], some of which gave partial
> success, but TB seems to miss these quite often even when they're
> staring it in the face. I'm sorry to report that the only 100% [so far]
> success I've had has been by rejecting messages from Gmail. I suspect
> that will also catch some genuine posters [inc Tony, the OP].

After trying a few other Subject strings in TB, I added individual Thai characters to the filter until it got rid of all of the existing messages - will see if any new ones get through later.

In my lunch break, I'm stuck with Google Groups. The best that can be done with that seems to be to use the Report Abuse function, but you still get "This conversation has been hidden because you've reported it for abuse" where each message was, rather than them disappearing altogether.

John Hall wrote:

> You could both try "=?UTF" for the subject

You'll find that catches-out people who include currency symbols
e.g. £, € etc or “smart quotes”.

On Wednesday, October 4, 2023 at 1:40:43 PM UTC+1, David North wrote:
> On Wednesday, 4 October 2023 at 09:56:54 UTC+1, Andy Walker wrote:
> > On 03/10/2023 23:50, Adrian wrote:
> > >> I've added another custom rule to reject /base64/h, I'll see what happens.
> > > That doesn't seem to have worked either.
> > I've tried various strings from the Subject [such as "ufa" and
> > "UTF-8"] and Injection-Info ["2a0e:a942"], some of which gave partial
> > success, but TB seems to miss these quite often even when they're
> > staring it in the face. I'm sorry to report that the only 100% [so far]
> > success I've had has been by rejecting messages from Gmail. I suspect
> > that will also catch some genuine posters [inc Tony, the OP].
> After trying a few other Subject strings in TB, I added individual Thai characters to the filter until it got rid of all of the existing messages - will see if any new ones get through later.
>
> In my lunch break, I'm stuck with Google Groups. The best that can be done with that seems to be to use the Report Abuse function, but you still get "This conversation has been hidden because you've reported it for abuse" where each message was, rather than them disappearing altogether.

if your using google, you can avoid the spam if you sign in and then star the posts or postees
you want, perhaps a bit time consuming at first, but then when u press starred conversations
the spam disapears. at least it worked like that for me at the library. i'm not in the least tech savvy
but isnt there an option where u can choose the language etc, so if u choose only english, anything
in thai wont appear? I'm not surpised it appears on google cos they dont really monitor these
groups, but surely your news provider or server would be concerned about this, cos as u say
someones gone to a lot of trouble.

mike

On 10/4/2023 5:40 AM, David North wrote:
> On Wednesday, 4 October 2023 at 09:56:54 UTC+1, Andy Walker wrote:
>> On 03/10/2023 23:50, Adrian wrote:
>>>> I've added another custom rule to reject /base64/h, I'll see what happens.
>>> That doesn't seem to have worked either.
>> I've tried various strings from the Subject [such as "ufa" and
>> "UTF-8"] and Injection-Info ["2a0e:a942"], some of which gave partial
>> success, but TB seems to miss these quite often even when they're
>> staring it in the face. I'm sorry to report that the only 100% [so far]
>> success I've had has been by rejecting messages from Gmail. I suspect
>> that will also catch some genuine posters [inc Tony, the OP].
>
> After trying a few other Subject strings in TB, I added individual Thai characters to the filter until it got rid of all of the existing messages - will see if any new ones get through later.
>
> In my lunch break, I'm stuck with Google Groups. The best that can be done with that seems to be to use the Report Abuse function, but you still get "This conversation has been hidden because you've reported it for abuse" where each message was, rather than them disappearing altogether.

Report abuse to the following email id from where the SPAM originated in
Vietnam.

If anybody thinks that this SPAM is being spread by people from
Thailand, I have a moon to sell you all.

Report Abuse:

Email
contact@minproxy.io
Address
208 Nguyen Huu Canh, 22 Ward, Binh Thanh, Ho Chi Minh 700000, Vietnam

In message <ko55bmF1deaU2@mid.individual.net>, Andy Burns
<usenet@andyburns.uk> writes
>John Hall wrote:
>
>> You could both try "=?UTF" for the subject
>
>You'll find that catches-out people who include currency symbols
>e.g. £, € etc or “smart quotes”.

If they include those in the subject line, I'm tempted to think that not
seeing their posts would be no big loss.
--
John Hall "[It was] so steep that at intervals the street broke into steps,
like a person breaking into giggles or hiccups, and then resumed
its sober climb, until it had another fit of steps."
Ursula K Le Guin "The Beginning Place"

On Wed, 4 Oct 2023 16:37:12 +0100, John Hall <john_nospam@jhall.co.uk>
wrote:

>In message <ko55bmF1deaU2@mid.individual.net>, Andy Burns
><usenet@andyburns.uk> writes
>>John Hall wrote:
>>
>>> You could both try "=?UTF" for the subject
>>
>>You'll find that catches-out people who include currency symbols
>>e.g. £, € etc or “smart quotes”.
>
>If they include those in the subject line, I'm tempted to think that not
>seeing their posts would be no big loss.
>
>
My filter was working and then it quit working and now the spam has
gone and it's not my filter doing it. Maybe the spammers have
outspammed themselves.

max.it

max.it wrote:

> now the spam has gone and it's not my filter doing it. Maybe the
> spammers have outspammed themselves.

Seems to have been knocked on the head at 10:06 BST

In message <04tUmRBi4SHlFwyu@jhall_nospamxx.co.uk>, John Hall
<john_nospam@jhall.co.uk> writes
>You could both try "=?UTF" for the subject, which I had some success
>with before trying the "base64" rule. (Since it's not a custom rule,
>the = and ? aren't control characters but are taken literally.) It
>might not work with Thunderbird if it's modern enough to know that
>=?UTF-8? is control info rather than supposed to be taken literally,
>though.
>

I tried that last night, and it didn't appear to stop anything.

Adrian
--
To Reply :
replace "bulleid" with "adrian" - all mail to bulleid is rejected
Sorry for the rigmarole, If I want spam, I'll go to the shops
Every time someone says "I don't believe in trolls", another one dies.

On Wednesday, October 4, 2023 at 7:48:30 PM UTC+1, Adrian wrote:
> In message <04tUmRBi4SHlFwyu@jhall_nospamxx.co.uk>, John Hall
> <john_...@jhall.co.uk> writes
> >You could both try "=?UTF" for the subject, which I had some success
> >with before trying the "base64" rule. (Since it's not a custom rule,
> >the = and ? aren't control characters but are taken literally.) It
> >might not work with Thunderbird if it's modern enough to know that
> >=?UTF-8? is control info rather than supposed to be taken literally,
> >though.
> >
> I tried that last night, and it didn't appear to stop anything.
> Adrian

its been sorted in the soc. groups i use, so hopefully they will get
around to uk. groups in due course. i suggest you just keep reporting it
so they realise its still ongoing.

mike