From: "mark at klomp dot org" <sourceware-bugzilla@sourceware.org>
To: overseers@sourceware.org
Subject: [Bug Infrastructure/31550] New: Distributed spam fighting scripts
Date: Mon, 25 Mar 2024 00:12:31 +0000 [thread overview]
Message-ID: <bug-31550-14326@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=31550
Bug ID: 31550
Summary: Distributed spam fighting scripts
Product: sourceware
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: Infrastructure
Assignee: overseers at sourceware dot org
Reporter: mark at klomp dot org
Target Milestone: ---
Our spamassassin setup is still going strong. But there is still
spam coming through. Christopher Faylor used to do daily scans of
everything that did got through, feed it into the spam database and
clean up the lists. He isn't doing that anymore and it does seem to
cause more spam to slip through. We need to make it so that his
scripts can be easily run by project/list maintainers to have distributed
spam fighting. The scripts should also trigger removal of the spam
from pipermail and inbox.sourceware.org.
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2024-03-25 0:12 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=bug-31550-14326@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.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).