Getting SPAM via mailing list ... what can I do about it?

[Arie van Wingerden]

Just got this spam via the mailing list address::
Australia Immigration Services ***@mail.com via
<https://support.google.com/mail/answer/1311182?hl=nl> sourceware.org

[Per Bothner]

Post by Arie van Wingerden
<https://support.google.com/mail/answer/1311182?hl=nl> sourceware.org

The mailing list software at sourceware.org seems to do a pretty good but not
perfect job of keeping out spam - the archive shows about one spam message per quarter.
Some of the ones that get through were caught by my own email provider or
client software (Thunderbird).

So it seems like a pretty minor problem. I could ask the SourceWare
administrators to fine-tune their spam filters, but I think they're
doing an adequate job. Some amount of spam is inevitable these days.

At some point it might make sense to move the mailing list from
sourceware (perhaps to a host that uses mailman 3),
but at this point IMO "it ain't broke".

[Arie van Wingerden]

Hi Per,

OK. Good to know that this is an exception!

BTW. I like Kawa very much! Kudos!

Languages like Kawa, developed by one person, often are less bloated, more
consistent and also more feature complete.

I intend to start using it for creating Android apps, but I'll first try
and make some stuff in Windows.

/Arie

Post by Per Bothner

Post by Arie van Wingerden
<https://support.google.com/mail/answer/1311182?hl=nl> sourceware.org

The mailing list software at sourceware.org seems to do a pretty good but not
perfect job of keeping out spam - the archive shows about one spam message per quarter.
Some of the ones that get through were caught by my own email provider or
client software (Thunderbird).
So it seems like a pretty minor problem. I could ask the SourceWare
administrators to fine-tune their spam filters, but I think they're
doing an adequate job. Some amount of spam is inevitable these days.
At some point it might make sense to move the mailing list from
sourceware (perhaps to a host that uses mailman 3),
but at this point IMO "it ain't broke".
--
--Per Bothner