On 2017-08-13, J. Clarke wrote:
> In article ,
> skybuck2...@hotmail.com says...
>>
>> I see two solutions:
> It would be really nice if someone could convince radical Islam that
> spammers are offensive to
In article ,
skybuck2...@hotmail.com says...
>
> I see two solutions:
>
> 1. We build new architecture or adept current one so it's more like a
> blockchain, have to calculate some hash before being able to post and upload
> and such.
>
Am Dienstag, 25. Juli 2017 07:13:51 UTC+2 schrieb Rustom Mody:
> Of late there has been an explosion of spam
> Thought it was only a google-groups (USENET?) issue and would be barred from
> the mailing list.
>
> But then find its there in the mailing list archives as well
> Typical example:
>
Yes, it's more "leaky," though that's not quite the term I'd use. Instead,
I'd say there are fewer checks. On the mailing list side of things, you
have all the Postfix bells and whistles, which stop a ton of crap, much of
it before the message is officially entered into the mail.python.org
system.
On Tue, 25 Jul 2017 21:44:22 +, Grant Edwards wrote:
> On 2017-07-25, Wildman via Python-list wrote:
>
>> The posts are being made through Google Groups. Forwarding
>> the posts with headers to groups-ab...@google.com might help.
>
> I never has in the past. I
breamore...@gmail.com wrote:
Hence why I asked a couple of weeks back why we don't just bin the existing
group and start afresh with a new, properly moderated group.
Someone would need to volunteer to be the moderator.
Also, moderation is something of a consenting-adults
thing on usenet. It's
On Wednesday, July 26, 2017 at 8:29:07 AM UTC+1, Tim Golden wrote:
> On 25/07/2017 06:13, Rustom Mody wrote:
> > Of late there has been an explosion of spam
> > Thought it was only a google-groups (USENET?) issue and would be barred
> > from the mailing list.
> >
> > But then find its there in
On 25/07/2017 06:13, Rustom Mody wrote:
Of late there has been an explosion of spam
Thought it was only a google-groups (USENET?) issue and would be barred from
the mailing list.
But then find its there in the mailing list archives as well
Typical example:
On 2017-07-25 10:03, alister wrote:
On Tue, 25 Jul 2017 17:29:56 +1000, Chris Angelico wrote:
On Tue, Jul 25, 2017 at 4:50 PM, wrote:
I see two solutions:
1. We build new architecture or adept current one so it's more like a
blockchain, have to calculate some hash
On 2017-07-25, Wildman via Python-list wrote:
> The posts are being made through Google Groups. Forwarding
> the posts with headers to groups-ab...@google.com might help.
I never has in the past. I (and many others) have for years and years
been plonking all posts made
On Mon, 24 Jul 2017 23:01:43 -0700, Paul Rubin wrote:
> Rustom Mody writes:
>> Since spammers are unlikely to be choosy about whom they spam:
>> Tentative conclusion: Something about the USENET-ML gateway is more leaky
>> out here than elsewhere
>
> It could be a sort-of
On Tue, 25 Jul 2017 17:29:56 +1000, Chris Angelico wrote:
> On Tue, Jul 25, 2017 at 4:50 PM, wrote:
>> I see two solutions:
>>
>> 1. We build new architecture or adept current one so it's more like a
>> blockchain, have to calculate some hash before being able to post
On Tue, Jul 25, 2017 at 4:50 PM, wrote:
> I see two solutions:
>
> 1. We build new architecture or adept current one so it's more like a
> blockchain, have to calculate some hash before being able to post and upload
> and such.
>
> or
>
> 2. We counter-attack by
I see two solutions:
1. We build new architecture or adept current one so it's more like a
blockchain, have to calculate some hash before being able to post and upload
and such.
or
2. We counter-attack by installing a special tool, so we all denial of service
attack the source of the
Rustom Mody writes:
> Since spammers are unlikely to be choosy about whom they spam:
> Tentative conclusion: Something about the USENET-ML gateway is more leaky
> out here than elsewhere
It could be a sort-of DOS attack by some disgruntled idiot. I wonder if
the email
15 matches
Mail list logo