From: "Robin H. Johnson" <robbat2@gentoo.org>
To: meta@public-inbox.org
Subject: more debugging for gentoo usage & supporting feature requests
Date: Mon, 22 Jul 2024 01:27:41 +0000 [thread overview]
Message-ID: <robbat2-20240722T011301-042174550Z@orbis-terrarum.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 2425 bytes --]
Hi,
I moved the Gentoo instance to a much beefier machine & newer kernel,
ingest is a lot faster; but there's still some hiccups.
1. Request for more debugging details about mails: Seems that many of
our oldest mails don't get ingested - and there's no output about why.
I don't know if -watch actually scanned that folder or not.
1.1. Possibly related:
Intended config is that the mail should be ingested regardless of the
email address on the headers. Way back in time, the Gentoo lists were
renamed a few times, and the files are sorted into the correct folders.
I think this impacted any attempted ingest via -mda because there's no
other way to override what list a given mail on stdin should be
associated with.
The headers may be inconsistent, changed style, name, or even be absent
in a few cases.
2.
What's the intended way for public-inbox-mda to function with no
SpamAssassin installed at all? "spamcheck = " doesn't seem to do it.
3.
As a formal feature request:
Change the arguments of: public-inbox-watch
- Add --all to mean all lists in the config
- no arguments => implicit --all
- $LISTNAME/$INBOXPATH => one *OR* more inboxes manually specified.
I did a hacky split of the configuration for Gentoo, and things are a
LOT more stable with 120 instances; but it's a little wasteful: I'd like
to give the high-traffic lists their own instance, and group the
low-traffic instances together.
Downside of my hacky code is that I have 120 processes that just say
"/usr/bin/public-inbox-watch", and I have to be creative to see which
list a given process is linked to.
4.
Make public-inbox-init NOT attempt to write to any configuration files.
Trying to implement segregation of roles:
- config files owned by root only; readable by public-inbox users.
- source maildirs read-only to user running public-inbox-watch
- public-inbox dirs writable to user running public-inbox-watch
- public-inbox dirs readable to user running public-inbox-httpd
Intent:
- public-inbox-httpd CANNOT read or write the source maildirs.
- public-inbox-watch CANNOT write the source maildirs.
- neither process can write the config file
--
Robin Hugh Johnson
Gentoo Linux: Dev, Infra Lead, Foundation President & Treasurer
E-Mail : robbat2@gentoo.org
GnuPG FP : 11ACBA4F 4778E3F6 E4EDF38E B27B944E 34884E85
GnuPG FP : 7D0B3CEB E9B85B1F 825BCECF EE05E6F6 A48F6136
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 1113 bytes --]
next reply other threads:[~2024-07-22 1:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-22 1:27 Robin H. Johnson [this message]
2024-07-22 6:23 ` more debugging for gentoo usage & supporting feature requests - infinite loop on disk full Robin H. Johnson
2024-07-22 19:44 ` Eric Wong
2024-07-23 21:30 ` Eric Wong
2024-07-22 19:40 ` more debugging for gentoo usage & supporting feature requests Eric Wong
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=robbat2-20240722T011301-042174550Z@orbis-terrarum.net \
--to=robbat2@gentoo.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).