From: Thomas Koenig <tkoenig@netcologne.de>
To: gcc mailing list <gcc@gcc.gnu.org>, overseers@gcc.gnu.org
Subject: Spam, bounces and gcc list removal
Date: Sun, 15 Mar 2020 13:24:15 +0100 [thread overview]
Message-ID: <82e9a365-63b1-93f6-9860-86f219e191be@netcologne.de> (raw)
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).
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?
Regards
Thomas
next reply other threads:[~2020-03-15 12:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-15 12:24 Thomas Koenig [this message]
2020-03-21 19:39 ` Thomas Koenig
2020-03-21 20:08 ` H.J. Lu
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=82e9a365-63b1-93f6-9860-86f219e191be@netcologne.de \
--to=tkoenig@netcologne.de \
--cc=gcc@gcc.gnu.org \
--cc=overseers@gcc.gnu.org \
/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).