From: Arie van Wingerden <xapwing@gmail.com>
To: per@bothner.com
Cc: kawa@sourceware.org
Subject: Re: Getting SPAM via mailing list ... what can I do about it?
Date: Tue, 30 Oct 2018 09:50:00 -0000 [thread overview]
Message-ID: <CADkALSEyQbOt=0-zhkXHwyGSVTdmug3agBNJ=TJ_4TAZKNrKVA@mail.gmail.com> (raw)
In-Reply-To: <763f9bbf-3523-552b-2849-49298c500aeb@bothner.com>
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
Op di 30 okt. 2018 om 02:38 schreef Per Bothner <per@bothner.com>:
> On 10/29/18 1:34 AM, Arie van Wingerden wrote:
> > Just got this spam via the mailing list address::
> > Australia Immigration Services immi.aus@mail.com via
> > <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
> per@bothner.com http://per.bothner.com/
>
prev parent reply other threads:[~2018-10-30 9:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-29 8:34 Arie van Wingerden
2018-10-30 1:38 ` Per Bothner
2018-10-30 9:50 ` Arie van Wingerden [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CADkALSEyQbOt=0-zhkXHwyGSVTdmug3agBNJ=TJ_4TAZKNrKVA@mail.gmail.com' \
--to=xapwing@gmail.com \
--cc=kawa@sourceware.org \
--cc=per@bothner.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).