From: "Maciej W. Rozycki" <macro@linux-mips.org>
To: "Frank Ch. Eigler" <fche@redhat.com>
Cc: Overseers mailing list <overseers@sourceware.org>,
overseers@gcc.gnu.org, gcc mailing list <gcc@gcc.gnu.org>,
Thomas Koenig <tkoenig@netcologne.de>
Subject: Re: Spam, bounces and gcc list removal
Date: Sat, 21 Mar 2020 21:22:31 +0000 (GMT) [thread overview]
Message-ID: <alpine.LFD.2.21.2003212110470.2689954@eddie.linux-mips.org> (raw)
In-Reply-To: <20200321202941.GA15063@redhat.com>
On Sat, 21 Mar 2020, Frank Ch. Eigler via Gcc wrote:
> > > So, a request: Could the overseers either install more effective
> > > spam protection for the list as a whole (preferred)
>
> Heh, if only it were that easy! Spam filtering was and is distinct
> from mailing list processing, and as you know it's a constant arms
> race. We're working hard to make the new installation of spamassassin
> as discriminating as possible. We're also working on the workflow to
> clean the web archives of spam that got through.
Spam bouncing is evil and often hits an innocent person whose address has
been faked by the sender of spam, making the source of bounces not better
than the originator. I have been hit myself like that in the past when
someone chose to use my address; fortunately I only received a mere 1000
of bounces or so. If caught and chosen not to be quarantined or stored in
a spambox, spam is best silently dropped on the floor aka /dev/null.
I would certainly recommend anyone making use of services provided by an
ISP who bounces spam to contact their e-mail system administrator and
enquire as to why they chose to do so. At worst I would change the ISP
for their bad practices, and I think the decision to unsubscribe people
whose ISP chose to bounce spam received through the mailing list is a
reasonable one.
Maciej
next prev parent reply other threads:[~2020-03-21 21:22 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
2020-03-22 2:39 ` Oleg Endo
2020-03-21 20:29 ` Frank Ch. Eigler
2020-03-21 21:22 ` Maciej W. Rozycki [this message]
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=alpine.LFD.2.21.2003212110470.2689954@eddie.linux-mips.org \
--to=macro@linux-mips.org \
--cc=fche@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=overseers@gcc.gnu.org \
--cc=overseers@sourceware.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).