From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <hjl.tools@gmail.com>
Received: from mail-ot1-x332.google.com (mail-ot1-x332.google.com
 [IPv6:2607:f8b0:4864:20::332])
 by sourceware.org (Postfix) with ESMTPS id 5A9A33877007;
 Sat, 21 Mar 2020 20:09:27 +0000 (GMT)
DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 5A9A33877007
Received: by mail-ot1-x332.google.com with SMTP id r2so9530585otn.6;
 Sat, 21 Mar 2020 13:09:27 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20161025;
 h=x-gm-message-state:mime-version:references:in-reply-to:from:date
 :message-id:subject:to:cc;
 bh=HgFS7CllDhj/y7/lsfaw9zSVSMm+TAnP1y4Ml7HGxq8=;
 b=ugHrGHhzy8aoMjwhK3Z7yFDKnTuyZrADunR8Hul/k7L9yunMCpeyYiyYsCCpvaHxSb
 7H1iu02PzuTGASl4BEDno4HFphhSc/PNbDezliL4mYQKpYFiHoKv03gFQieHC3VapUHA
 aISpQFnOZzWlnIBuAHE7d9TxBPa5pJQO7Bk0gkMoBwkFm6jawj9hnjFaqvBkbY30pm3q
 fTx+lDN7d3wOD7NxTVOppHB+GoNP+8tycxBku4+/w/YJGyB82ZNYrxSNenk4JrL0yl7i
 rguDA0onItjbVr7gh/eLu1+/4PKGDvLXknq/+iZVZH2N8sJ+dXr4xsImxU6OZKlKZIjW
 avZg==
X-Gm-Message-State: ANhLgQ36rXKMeSc9MIU5exE20c4152N917hVoZ9NrW0sCh253l2mtzAM
 7JnToW1B7aPkvzHkAAfVzckzCtysHxuDtMKSKEM=
X-Google-Smtp-Source: ADFU+vtxGWmgMKi4lTrH3GUZTvnNq53A2XIBp/FjIAKlrtIGmLwKGPhXnXP+nR2lha7YHKkpva1xXoSrrkpk6H1IKF8=
X-Received: by 2002:a9d:23e4:: with SMTP id t91mr12107383otb.125.1584821366658; 
 Sat, 21 Mar 2020 13:09:26 -0700 (PDT)
MIME-Version: 1.0
References: <82e9a365-63b1-93f6-9860-86f219e191be@netcologne.de>
 <e7053f50-16a1-b694-c519-fe91e573b71a@netcologne.de>
In-Reply-To: <e7053f50-16a1-b694-c519-fe91e573b71a@netcologne.de>
From: "H.J. Lu" <hjl.tools@gmail.com>
Date: Sat, 21 Mar 2020 13:08:50 -0700
Message-ID: <CAMe9rOqsQqUtxDCnYn7Hr=wVA0Eb+jbP8cyJ2s+dLL0541R7qg@mail.gmail.com>
Subject: Re: Spam, bounces and gcc list removal
To: Thomas Koenig <tkoenig@netcologne.de>
Cc: gcc mailing list <gcc@gcc.gnu.org>, overseers@gcc.gnu.org
Content-Type: text/plain; charset="UTF-8"
X-Spam-Status: No, score=-8.9 required=5.0 tests=BAYES_00, DKIM_SIGNED,
 DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, FREEMAIL_FROM, RCVD_IN_DNSWL_NONE,
 SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.2
X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on
 server2.sourceware.org
X-BeenThere: overseers@sourceware.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Overseers mailing list <overseers.sourceware.org>
List-Unsubscribe: <http://sourceware.org/mailman/options/overseers>,
 <mailto:overseers-request@sourceware.org?subject=unsubscribe>
List-Archive: <http://sourceware.org/pipermail/overseers/>
List-Post: <mailto:overseers@sourceware.org>
List-Help: <mailto:overseers-request@sourceware.org?subject=help>
List-Subscribe: <http://sourceware.org/mailman/listinfo/overseers>,
 <mailto:overseers-request@sourceware.org?subject=subscribe>
X-List-Received-Date: Sat, 21 Mar 2020 20:09:28 -0000

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.