public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: "Frank Ch. Eigler" <fche@elastic.org>
To: Overseers mailing list <overseers@sourceware.org>
Cc: Ian Kelling <iank@fsf.org>
Subject: Re: How does sourceware handle spam sent to Mailman?
Date: Thu, 8 Dec 2022 21:44:33 -0500	[thread overview]
Message-ID: <Y5KhESU6m+6DO5S2@elastic.org> (raw)
In-Reply-To: <87359pikgp.fsf@fsf.org>

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

      parent reply	other threads:[~2022-12-09  2:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-08 22:40 Ian Kelling
2022-12-09  0:26 ` Jose E. Marchesi
2022-12-09  2:44 ` Frank Ch. Eigler [this message]

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=Y5KhESU6m+6DO5S2@elastic.org \
    --to=fche@elastic.org \
    --cc=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).