From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from cvs.linux-mips.org (eddie.linux-mips.org [148.251.95.138]) by sourceware.org (Postfix) with ESMTP id A33FA3877007; Sat, 21 Mar 2020 21:22:33 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org A33FA3877007 Received: (from localhost user: 'macro', uid#1010) by eddie.linux-mips.org with ESMTP id S23992263AbgCUVWbQEic5 (ORCPT + 1 other); Sat, 21 Mar 2020 22:22:31 +0100 Date: Sat, 21 Mar 2020 21:22:31 +0000 (GMT) Sender: "Maciej W. Rozycki" From: "Maciej W. Rozycki" To: "Frank Ch. Eigler" cc: Overseers mailing list , overseers@gcc.gnu.org, gcc mailing list , Thomas Koenig Subject: Re: Spam, bounces and gcc list removal In-Reply-To: <20200321202941.GA15063@redhat.com> Message-ID: References: <82e9a365-63b1-93f6-9860-86f219e191be@netcologne.de> <20200321202941.GA15063@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII X-Spam-Status: No, score=-6.1 required=5.0 tests=BAYES_00, KAM_DMARC_STATUS, KAM_LAZY_DOMAIN_SECURITY, RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, SPF_NONE, TXREP, UNPARSEABLE_RELAY autolearn=no 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: Sat, 21 Mar 2020 21:22:49 -0000 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