From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from atuin.qyliss.net (localhost [IPv6:::1]) by atuin.qyliss.net (Postfix) with ESMTP id 75B2024AA3; Wed, 02 Jul 2025 09:26:12 +0000 (UTC) Received: by atuin.qyliss.net (Postfix, from userid 993) id 99A4024A9C; Wed, 02 Jul 2025 09:26:09 +0000 (UTC) X-Spam-Checker-Version: SpamAssassin 4.0.1 (2024-03-26) on atuin.qyliss.net X-Spam-Level: X-Spam-Status: No, score=-0.8 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,DMARC_MISSING,RCVD_IN_DNSWL_LOW,SPF_HELO_PASS autolearn=unavailable autolearn_force=no version=4.0.1 Received: from fhigh-b8-smtp.messagingengine.com (fhigh-b8-smtp.messagingengine.com [202.12.124.159]) by atuin.qyliss.net (Postfix) with ESMTPS id 3E56B24A9A for ; Wed, 02 Jul 2025 09:26:07 +0000 (UTC) Received: from phl-compute-04.internal (phl-compute-04.phl.internal [10.202.2.44]) by mailfhigh.stl.internal (Postfix) with ESMTP id E93DA7A0009; Wed, 2 Jul 2025 05:26:04 -0400 (EDT) Received: from phl-mailfrontend-02 ([10.202.2.163]) by phl-compute-04.internal (MEProxy); Wed, 02 Jul 2025 05:26:05 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=alyssa.is; h=cc :cc:content-type:content-type:date:date:from:from:in-reply-to :in-reply-to:message-id:mime-version:references:reply-to:subject :subject:to:to; s=fm1; t=1751448364; x=1751534764; bh=bUknCLOfRq avpsdE8wJLgxN7btCXiXyp9n/BSsg/I48=; b=lrFY619D3QppK2FlZxUc9JwRWH cjpWpPe4+jeGxY1OdXDPRoxXanLOqFVKfmHq90w5POJ6UAfqmW6loLX1KlxRlpzO Sfebmk8vIg6GAy5nDzbEIWTmaEl16nRi3HoShnSkX/owxlwfkJbKX2FhdAF7Zxlx gBvZ0VXSRYJfAc51oUQhVgD1ITP65YJ2rIXcDoIe90/7YMUXGpx7EhXv2Cb4MPnp llEZ3dEpev6zZdLB/CLOnJt3Mbdeh0j82rv7J0xoCdDXF3Kog99lqIOpkPBXZCGd da1ncfGP2c0BHJjlBFGtAn4dcymYwbcJTiLxMEZQqmk8bmmDkeByfrML1rjA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-type:content-type:date:date :feedback-id:feedback-id:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:subject:subject:to :to:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; t= 1751448364; x=1751534764; bh=bUknCLOfRqavpsdE8wJLgxN7btCXiXyp9n/ BSsg/I48=; b=il7wZ7IcSJiL5zwVnErKSSpZrBs45LQWzwNiFH3TmqenY0MKYwY QEor1UWppG3MzUfsE5oUCLR/uXt+1Cxwae2SR8kBhqhghonULyPdypbsYnpbViWp je3UxCxrxGSDVTFkUc/v6KlromrfY4AMjDQOXtvPVQiK29szZjDsji/43okumjnK AIFTEU4w5o9+sbjugYRvvwKgbxzhHh8i73UOc0/GwrzaFLUeu6zVrNTNgu5FfUhE vyU59Gy8SEXg4KbW9grbi61xDz7vuTXwtZUbBrQTrVHQZh1lxW+DwSjv+v9G4oGF iL4dbKcgeoUvaCK6h73NWTjTqkYU3QBf3rQ== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeeffedrtdefgddujedtfecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpuffrtefokffrpgfnqfghnecuuegr ihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenucfjug hrpefhvfevufgjfhffkfggtgesghdtreertddttdenucfhrhhomheptehlhihsshgrucft ohhsshcuoehhihesrghlhihsshgrrdhisheqnecuggftrfgrthhtvghrnhephfevleevvd eiveekiefhudetgeehjeekhefhfffgjeehgfeuvdejjeefledtueeknecuffhomhgrihhn pehgnhhurdhorhhgnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilh hfrhhomhephhhisegrlhihshhsrgdrihhspdhnsggprhgtphhtthhopeefpdhmohguvgep shhmthhpohhuthdprhgtphhtthhopegrtghuthgvrggrnhhglhgvseguihhsrhhoohhtrd horhhgpdhrtghpthhtohepshhhhihmvghgrgesshhhhihmvghgrgdrohhrghdruhhkpdhr tghpthhtohepughishgtuhhsshesshhpvggtthhruhhmqdhoshdrohhrgh X-ME-Proxy: Feedback-ID: i12284293:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Wed, 2 Jul 2025 05:26:04 -0400 (EDT) Received: by sf.qyliss.net (Postfix, from userid 1000) id 7329F266BC8A7; Wed, 02 Jul 2025 11:26:03 +0200 (CEST) From: Alyssa Ross To: Summer Tea , "Dom (shymega) Rodriguez" Subject: Re: Anti-spam. In-Reply-To: <8c39516778489e5c3fe65ed7dfac9c37@disroot.org> References: <8c39516778489e5c3fe65ed7dfac9c37@disroot.org> Date: Wed, 02 Jul 2025 11:26:01 +0200 Message-ID: <877c0r7xli.fsf@alyssa.is> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature" Message-ID-Hash: ICUCZHOQGAIJCX4KOYTNAHP622YYHMTO X-Message-ID-Hash: ICUCZHOQGAIJCX4KOYTNAHP622YYHMTO X-MailFrom: hi@alyssa.is X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-discuss.spectrum-os.org-0; header-match-discuss.spectrum-os.org-1; header-match-discuss.spectrum-os.org-2; header-match-discuss.spectrum-os.org-3; header-match-discuss.spectrum-os.org-4; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header CC: discuss@spectrum-os.org X-Mailman-Version: 3.3.9 Precedence: list List-Id: General high-level discussion about Spectrum Archived-At: List-Archive: List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: --=-=-= Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Summer Tea writes: > I am unsure what the current configuration is; however, I believe=20 > Mailman supports holding messages from non-members for moderator=20 > approval. > > https://www.gnu.org/software/mailman/mailman-admin/sender-filters.html The current configuration is that incoming mail is run through SpamAssassin, then passed on to Mailman. Any message marked as spam by SpamAssassin is held by Mailman for review, as is any message containing an HTML part, because those are much more likely to be spam. I use the default SpamAssassin rules, plus the ones that come with public-inbox. When a spam message makes it through, I run it through public-inbox-learn spam to remove it from the archive and train SpamAssassin. I don't want to require subscription to post to the list, because as a contributor to other projects I find that quite unfriendly, particularly when I'm not intending to become a recurring contributor and so have no need to receive messages from the list. With that of course comes the inability to 100% prevent spam, but I don't think we quite need 100%. This is how the kernel lists work as well, for example. The spam we've been receiving most recently doesn't look suspicious at all to SpamAssassin: nothing weird about the headers; no obviously problematic phrases. One obvious thing that we could do for this type of message in particular would be to hold messages written in languages other than English. I'll do that as the next step, but also open to further suggestions. --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iHUEARYKAB0WIQRV/neXydHjZma5XLJbRZGEIw/wogUCaGT7KQAKCRBbRZGEIw/w osbKAPsEe038G3ek+4zykY0fsh3t5S9ZwI8301EYcLY4NKEpDwEAo82YXTQDB9f+ g+7SPLZ1P1rM0D7R7VGRnst0LYWlaAA= =A1HW -----END PGP SIGNATURE----- --=-=-=--