From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from elastic.org (elastic.org [96.126.110.187]) by sourceware.org (Postfix) with ESMTPS id 1E1B7388EC3D for ; Fri, 9 Dec 2022 02:44:35 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 1E1B7388EC3D Authentication-Results: sourceware.org; dmarc=pass (p=quarantine dis=none) header.from=elastic.org Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=elastic.org DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=elastic.org ; s=default2; h=In-Reply-To:Content-Type:MIME-Version:References:Message-ID: Subject:Cc:To:From:Date:Sender:Reply-To:Content-Transfer-Encoding:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=AmKJ50OU2UXv2QtfYc/MF15/cBMTo3B4UE7wa20+3EM=; b=ZsY8K8ASpg/KK5czwJme/ZmpL/ nYXxiQrJvpqOXAQhyzhAAUD8RuOFrRz9rVq/lA+mgvJnZq9P9VFrUV+ev8d0PmWvxZGxjpMRobHWx STWstyDM4KFSt+ery0GU5wc6M0b1htN74Ss2COAysRrp3B1NZ7Ln4XDvJfmvqlOM4pIdwJs3O5BPm KY4R+xlP0ZVSXHUVUFMfimTa+z07O5k+O++ZeEv6x1HCGbFLKHr7nx4d44iRGrh6VIQzoxKVYRMA3 MIBH8/pE4aCIPgdZEHAJjvQKOYOuKfTDN6CVPJvvX2VRq+9apNsqbhEC/HEymP3xoxsbtn7hRpB8T 1BhFg9LA==; Received: from vpn-home.elastic.org ([10.0.0.2] helo=elastic.org) by elastic.org with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1p3TNK-0004bB-0I; Fri, 09 Dec 2022 02:44:34 +0000 Received: from dhcp25.elastic.org ([192.168.1.125] helo=very.elastic.org) by elastic.org with esmtp (Exim 4.96) (envelope-from ) id 1p3TNJ-000Bp9-2Z; Thu, 08 Dec 2022 21:44:33 -0500 Received: from fche by very.elastic.org with local (Exim 4.96) (envelope-from ) id 1p3TNJ-000GFf-2N; Thu, 08 Dec 2022 21:44:33 -0500 Date: Thu, 8 Dec 2022 21:44:33 -0500 From: "Frank Ch. Eigler" To: Overseers mailing list Cc: Ian Kelling Subject: Re: How does sourceware handle spam sent to Mailman? Message-ID: References: <87359pikgp.fsf@fsf.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <87359pikgp.fsf@fsf.org> X-Sender-Verification: "" X-Spam-Status: No, score=-101.7 required=5.0 tests=BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,SPF_HELO_PASS,SPF_PASS,TXREP,USER_IN_WELCOMELIST,USER_IN_WHITELIST autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: Hi - So far, our postfix-tied copy of spamassassin and related tooling has done okay at blocking the vast majority of incoming spam before it hits mailman, and without interfering with moderation or list management approvals. (We could use some better machinery for handling the few evaders that pass through.) - FChE