public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Thomas Koenig <tkoenig@netcologne.de>
To: "Frank Ch. Eigler" <fche@redhat.com>,
	Overseers mailing list <overseers@sourceware.org>
Cc: overseers@gcc.gnu.org, gcc mailing list <gcc@gcc.gnu.org>
Subject: Re: Spam, bounces and gcc list removal
Date: Sun, 22 Mar 2020 10:54:30 +0100	[thread overview]
Message-ID: <97dcb3a4-a983-f3f8-d90f-a4932aeee3ab@netcologne.de> (raw)
In-Reply-To: <20200321202941.GA15063@redhat.com>

Am 21.03.20 um 21:29 schrieb Frank Ch. Eigler via Gcc:
> 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
> 
> For my reference, could you forward one of these spams & bounces to me?

I never got to see them, because they never made it past my ISP.

>>> 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.

That makes it even less likely that I will be able to provide you with
a sample, unfortunately.

Maybe it would be better just to look at the logfiles?  You will
probably see a

  550 5.7.1 Refused by local policy. No SPAM please!

or similar there.

>>> or relax the limit on bounces?
> 
> OK, there are a couple of settings over at:
> https://gcc.gnu.org/mailman/admin/gcc/bounce
> that law and we can think about, but I'd like
> to see the messages in question to figure out what happened.

Maybe it is possible to do it like the old mail system did:

If there were too many bounces, it sent a probe, if that didn't
bounce, nothing more happened.

That worked OK, the current system does not.

Regards

	Thomas

      parent reply	other threads:[~2020-03-22  9:54 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
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 [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=97dcb3a4-a983-f3f8-d90f-a4932aeee3ab@netcologne.de \
    --to=tkoenig@netcologne.de \
    --cc=fche@redhat.com \
    --cc=gcc@gcc.gnu.org \
    --cc=overseers@gcc.gnu.org \
    --cc=overseers@sourceware.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).