public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: "H.J. Lu" <hjl.tools@gmail.com>
To: Thomas Koenig <tkoenig@netcologne.de>
Cc: gcc mailing list <gcc@gcc.gnu.org>, overseers@gcc.gnu.org
Subject: Re: Spam, bounces and gcc list removal
Date: Sat, 21 Mar 2020 13:08:50 -0700	[thread overview]
Message-ID: <CAMe9rOqsQqUtxDCnYn7Hr=wVA0Eb+jbP8cyJ2s+dLL0541R7qg@mail.gmail.com> (raw)
In-Reply-To: <e7053f50-16a1-b694-c519-fe91e573b71a@netcologne.de>

On Sat, Mar 21, 2020 at 12:40 PM Thomas Koenig via Gcc <gcc@gcc.gnu.org> wrote:
>
> Hi,
>
> > since the change to the new list management, there has been
> > an uptick of spam getting through. Spam is bounced by my ISP,
> > and this just resulted in a warning that there were too many
> > bounces and that I would get removed from the list unless I
> > confirmed it (which I then did).
> This has now happened a second time, and this question

Same here.

> > So, a request: Could the overseers either install more effective
> > spam protection for the list as a whole (preferred) or relax the
> > limit on bounces?
>
> is still valid.
>
> Some kind of reaction would be appreciated.
>
> Regards
>
>         Thomas
>
>


-- 
H.J.

  reply	other threads:[~2020-03-21 20:09 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-15 12:24 Thomas Koenig
2020-03-21 19:39 ` Thomas Koenig
2020-03-21 20:08   ` H.J. Lu [this message]
2020-03-22  2:39     ` Oleg Endo
2020-03-21 20:29   ` Frank Ch. Eigler
2020-03-21 21:22     ` Maciej W. Rozycki
2020-03-22  8:01       ` Winfried Magerl
2020-03-22 16:35         ` Maciej W. Rozycki
2020-03-22  9:05       ` Florian Weimer
2020-03-22 13:24         ` Maciej W. Rozycki
2020-03-22 13:29           ` Florian Weimer
2020-03-22 16:13             ` Maciej W. Rozycki
2020-03-22  9:54     ` Thomas Koenig

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='CAMe9rOqsQqUtxDCnYn7Hr=wVA0Eb+jbP8cyJ2s+dLL0541R7qg@mail.gmail.com' \
    --to=hjl.tools@gmail.com \
    --cc=gcc@gcc.gnu.org \
    --cc=overseers@gcc.gnu.org \
    --cc=tkoenig@netcologne.de \
    /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).