From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: meta@public-inbox.org
Subject: RFE: public-inbox-learn should skip inboxes it cannot write to
Date: Thu, 24 Oct 2024 13:21:22 -0400 [thread overview]
Message-ID: <20241024-nimble-honest-stallion-dad849@lemur> (raw)
Good day!
Our main aggregator system has inboxes from various sources -- some received
via email locally, some mirrored from other locations and owned by a different
user. They are all mentioned in the same config file, since they are all
replicated to frontends.
While trying to purge some trolling messages from the archives today using
"public-inbox-learn --all rm", I've discovered that public-inbox-learn will
crash if it's unable to modify an inbox (because it's owned by a different
user "mirror").
Preferably, it would just skip the inboxes to which it doesn't have write
access instead of crashing.
-K
reply other threads:[~2024-10-24 17:28 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
List information: https://public-inbox.org/README
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20241024-nimble-honest-stallion-dad849@lemur \
--to=konstantin@linuxfoundation.org \
--cc=meta@public-inbox.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).