From: Ian Kelling <iank@fsf.org>
To: overseers@sourceware.org
Subject: How does sourceware handle spam sent to Mailman?
Date: Thu, 08 Dec 2022 17:40:00 -0500 [thread overview]
Message-ID: <87359pikgp.fsf@fsf.org> (raw)
We have a good system setup on lists.gnu.org called listhelper,
https://savannah.gnu.org/maintenance/ListHelperAntiSpam/. The listhelper
system also runs for some third party mailman servers. I thought it
would be useful to compare notes and maybe the listhelper system could
help sourceware in some way.
--
Ian Kelling | Senior Systems Administrator, Free Software Foundation
GPG Key: B125 F60B 7B28 7FF6 A2B7 DF8F 170A F0E2 9542 95DF
https://fsf.org | https://gnu.org
next reply other threads:[~2022-12-08 22:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-08 22:40 Ian Kelling [this message]
2022-12-09 0:26 ` Jose E. Marchesi
2022-12-09 2:44 ` Frank Ch. Eigler
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=87359pikgp.fsf@fsf.org \
--to=iank@fsf.org \
--cc=overseers@sourceware.org \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).