From: Alyssa Ross <hi@alyssa.is>
To: Summer Tea <acuteaangle@disroot.org>,
"Dom (shymega) Rodriguez" <shymega@shymega.org.uk>
Cc: discuss@spectrum-os.org
Subject: Re: Anti-spam.
Date: Wed, 02 Jul 2025 11:26:01 +0200 [thread overview]
Message-ID: <877c0r7xli.fsf@alyssa.is> (raw)
In-Reply-To: <8c39516778489e5c3fe65ed7dfac9c37@disroot.org>
[-- Attachment #1: Type: text/plain, Size: 1573 bytes --]
Summer Tea <acuteaangle@disroot.org> writes:
> I am unsure what the current configuration is; however, I believe
> Mailman supports holding messages from non-members for moderator
> 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.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2025-07-02 9:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-01 22:59 Anti-spam Dom (shymega) Rodriguez
2025-07-02 8:58 ` Anti-spam Summer Tea
2025-07-02 9:26 ` Alyssa Ross [this message]
2025-07-02 13:42 ` Anti-spam Alyssa Ross
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=877c0r7xli.fsf@alyssa.is \
--to=hi@alyssa.is \
--cc=acuteaangle@disroot.org \
--cc=discuss@spectrum-os.org \
--cc=shymega@shymega.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).