From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from albireo.enyo.de (albireo.enyo.de [37.24.231.21]) by sourceware.org (Postfix) with ESMTPS id DBC9D3887023; Sun, 22 Mar 2020 09:06:33 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org DBC9D3887023 Received: from [172.17.203.2] (helo=deneb.enyo.de) by albireo.enyo.de with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) id 1jFwYw-0008Mi-Vu; Sun, 22 Mar 2020 09:06:30 +0000 Received: from fw by deneb.enyo.de with local (Exim 4.92) (envelope-from ) id 1jFwXd-0001ED-Q0; Sun, 22 Mar 2020 10:05:09 +0100 From: Florian Weimer To: "Maciej W. Rozycki" Cc: "Frank Ch. Eigler" , overseers@gcc.gnu.org, gcc mailing list , Overseers mailing list , Thomas Koenig Subject: Re: Spam, bounces and gcc list removal References: <82e9a365-63b1-93f6-9860-86f219e191be@netcologne.de> <20200321202941.GA15063@redhat.com> Date: Sun, 22 Mar 2020 10:05:09 +0100 In-Reply-To: (Maciej W. Rozycki's message of "Sat, 21 Mar 2020 21:22:31 +0000 (GMT)") Message-ID: <87k13c4v5m.fsf@mid.deneb.enyo.de> MIME-Version: 1.0 Content-Type: text/plain X-Spam-Status: No, score=-12.6 required=5.0 tests=BAYES_00, KAM_DMARC_STATUS, 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 22 Mar 2020 09:06:35 -0000 * Maciej W. Rozycki: > 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 expect this to be an SMTP-level rejection, not a bounce. sourceware generates a bounce from that, and Mailman reacts to that. But the target mail server does not generate a bounce. So your concern about bad ISP behavior does not apply here.