Thankfully, spam should subside soon as Google (the company that has
amassed the most mental defectives in the world) is shutting down Google
Groups Usenet https://support.google.com/groups/answer/11036538?hl=en

The best part of that article is they don't mention all the spam is
coming from their service.

On 15-12-2023 17:20, Kevin Bowling wrote:
> Thankfully, spam should subside soon as Google (the company that has amassed the most mental defectives in the world) is shutting down Google Groups Usenet https://support.google.com/groups/answer/11036538?hl=en
>
> The best part of that article is they don't mention all the spam is coming from their service.

Ooooh, but they do, Kevin:

"Much of the content being disseminated via Usenet today is binary (non-text) file sharing, which Google Groups does not support, as well as spam."

What they left out between the word 'spam' and the full stop is : ", which Google Groups *does* support".

Just to keep the sentence short ;-)))

--
Jelte,
Admirer of the letter of IBM with blue Ishiki

On 16/12/23 00:20, Kevin Bowling wrote:
> Thankfully, spam should subside soon as Google (the company that has
> amassed the most mental defectives in the world) is shutting down Google
> Groups Usenet https://support.google.com/groups/answer/11036538?hl=en
>
> The best part of that article is they don't mention all the spam is
> coming from their service.
is going to be harder but not impossible!

always worked for me

1- Use proper News Client
2- use filter
3- Do not respond to their spam, not even for sarcastic comments

--
Moussa

"People alike with a similar circumstances, tend to find each
others across space and time, given enough time in life, no
matter distance, language, race, colour and believes" (c) MEK
*** Do Not Copy, Duplicate or Use without my Permission ***

Moussa, I have listened to Filter... Hey Man, nice shot comes to mind.

But what do you filter on when the titles vary so widely and the
accounts are most likely harvested?

moussa wrote:
> 2- use filter

On 17/12/23 22:02, Louis Ohland wrote:
> Moussa, I have listened to Filter... Hey Man, nice shot comes to mind.
>
> But what do you filter on when the titles vary so widely and the
> accounts are most likely harvested?
>
> moussa wrote:
>> 2- use filter

a combination of keywords in sender email, subject and body

you could also do the reverse, what I call a whitelist

"if not from those people delete" <---you be missing new comers but you
can add those as you go later on.

My setup has varied over the years ATM I am using Thunderbird through
leaf-node to Kevin server

I don't understand why not give those mini pc a new life by fortifying
their Internet connection for few $$!, the power usage would be hardly
noticeable and they are silent.

{WAN}---[VDSL/router]------[IPFire]----[PIhole]

--
Moussa

"People alike with a similar circumstances, tend to find each
others across space and time, given enough time in life, no
matter distance, language, race, colour and believes" (c) MEK
*** Do Not Copy, Duplicate or Use without my Permission ***

> Kevin Bowling wrote:
> Thankfully, spam should subside soon as Google (the company that
has
> amassed the most mental defectives in the world) is shutting down
Google
> Groups Usenet
https://support.google.com/groups/answer/11036538?hl=en
>
> The best part of that article is they don't mention all the spam is

> coming from their service.

Did a little digging and found the culprit of the mass spamming on
Google Groups is using some service called "DeepLeo" to do
their spamming and automated article writing. Found a DeepLeo on
Github and seems to be some sort of interface with ChatGPT

It was only a matter of time before that resource was utilized for
that type of bad activity.

This is a response to the post seen at:
http://www.jlaforums.com/viewtopic.php?p=657403065#657403065

Someone can ask ChatGPT to write the technical reference for the
Fast/Wide SCSI-2 Adapter /A

MummyChunk wrote:
> Did a little digging and found the culprit of the mass spamming on
> Google Groups is using some service called "DeepLeo" to do
> their spamming and automated article writing. Found a DeepLeo on
> Github and seems to be some sort of interface with ChatGPT
>
> It was only a matter of time before that resource was utilized for
> that type of bad activity.

> > Someone can ask ChatGPT to write the technical reference for the

> > Fast/Wide SCSI-2 Adapter /A
> >
> > MummyChunk wrote:
> > Did a little digging and found the culprit of the mass spamming
on
> > Google Groups is using some service called "DeepLeo" to
do
> > their spamming and automated article writing. Found a DeepLeo
on
> > Github and seems to be some sort of interface with ChatGPT
> >
> > It was only a matter of time before that resource was utilized
for
> > that type of bad activity.46e]

Here is what a basic version of it spit out when asked to do exactly
that. Probably could be more detailed if the question was changed.

The IBM PS/2 Microchannel Fast/Wide SCSI-2 Adapter /A is a controller
that allows you to connect SCSI devices to your computer. It is
supported on the MCA systems with an IML Partition 1. The adapter is
capable of supporting up to seven SCSI devices 2.

To add a narrow SCSI device to the FAST/WIDE SCSI Adapter /A, follow
these special instructions for configuring wide controllers to disable
wide messaging

Without the wide drive attached, start the system and press F1 while
the system is booting to start the configuration program.

Choose “Set Configuration”.

From the next menu choose “change configuration”.

Press F8 until the Fast/Wide SCSI adapter settings are displayed.

Find the line that says “Wide SCSI Messages - Internal” and choose
“Disable” (Use the F5 key to toggle Enable/Disable).

Ensure that the next line for Internal/External busses is set to
“Separate”.

Choose F10 to save, then F3 as needed to exit and restart.

Power off system and attach wide drive to SCSI and power connections.

Restart system and choose F1 again.

Again, decline auto configuration, instead choose “set
Configuration”.

Choose “Set and View SCSI configuration”.

The device should now appear at the ID it is configured for and at the
proper size. If so - save and restart system.

If the device is shown at the wrong size, incorrect termination on the
SCSI bus may be indicated - check termination and placement of
terminating devices on the SCSI cable.

This is a response to the post seen at:
http://www.jlaforums.com/viewtopic.php?p=657403065#657403065