public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Mark Wielaard <mark@klomp.org>
To: Overseers mailing list <overseers@sourceware.org>
Cc: Simon Marchi <simon.marchi@polymtl.ca>
Subject: Re: inbox.sourceware.org experiment
Date: Wed, 24 Aug 2022 12:05:03 +0200	[thread overview]
Message-ID: <YwX3zyp8d6GsHlG+@wildebeest.org> (raw)
In-Reply-To: <YwVP8+LHvyLzUG/+@wildebeest.org>

Hi,

On Wed, Aug 24, 2022 at 12:08:51AM +0200, Mark Wielaard via Overseers wrote:
> Sorry this took a bit longer. But I wanted to make sure I got it right.
> I solved it slightly simpler by installing a /home/inbox/.forward with:
> |/usr/bin/public-inbox-mda

This is now |/home/inbox/public-inbox-mda-true.sh
Which does:
/usr/bin/public-inbox-mda --no-precheck 2>&1 | ts >> /home/inbox/log/public-inbox-mda.out.log || true

|| true to make sure any errors don't cause a bounce.  --no-precheck
because public-inbox-mda is very picky and rejects various emails that
seem just fine. And a timestamped log of errors goes to
/home/inbox/log/public-inbox-mda.out.log

> And then simply add the inbox user as extra recipient. So the STANZA
> looks like:
> 
> # STANZA START: test-list
> # CREATED: Sat Mar  7 13:49:45 2020
> test-list:             "|/usr/local/mailman/mailman post test-list", inbox
> test-list-bounces:     "|/usr/local/mailman/mailman bounces test-list"
> test-list-confirm:     "|/usr/local/mailman/mailman confirm test-list"
> test-list-join:        "|/usr/local/mailman/mailman join test-list"
> test-list-leave:       "|/usr/local/mailman/mailman leave test-list"
> test-list-owner:       "|/usr/local/mailman/mailman owner test-list"
> test-list-request:     "|/usr/local/mailman/mailman request test-list"
> test-list-subscribe:   "|/usr/local/mailman/mailman subscribe test-list"
> test-list-unsubscribe: "|/usr/local/mailman/mailman unsubscribe test-list"
> # STANZA END: test-list
> 
> The script to generate those is in
> /etc/mailman/mailman-aliases-to-inbox.sh
> And the postfix main.cf has been updated to use the generated
> /etc/mailman/aliases-inbox

This was a little too naive, public-inbox-mda does ignore emails to
addresses it doesn't know about, but some addresses generated odd/bad
loops. In particular the "root" list (now removed by Frank) and the
mailman and postmaster lists (I removed the inbox recipient by hand).

The script really should be updated to only add inbox to those mailman
post lists it is archiving.

> The only thing I don't know is how to automate the
> /etc/mailman/mailman-aliases-to-inbox.sh running when new lists are
> added. Should this be a mailman trigger or cronjob check?

So once automated make sure the above changes are also done
automatically.

I noticed two issues some lists seem to have a bad/corrupt xapian
database and generate an error while indexing (gcc-patches). emails
with slashes / in the Message-ID sometimes get wrongly escaped and
appear to not be in the archive while they really are.
e.g. the message I am replying to shows as:
https://inbox.sourceware.org/overseers/YwVP8+LHvyLzUG%2F+@wildebeest.org/
But should be:
https://inbox.sourceware.org/overseers/YwVP8+LHvyLzUG/+@wildebeest.org/

Cheers,

Mark

  reply	other threads:[~2022-08-24 10:05 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-13 14:14 Mark Wielaard
2022-08-15 13:00 ` Mark Wielaard
2022-08-16 21:36 ` Mark Wielaard
2022-08-16 22:10   ` Frank Ch. Eigler
2022-08-17 12:25     ` Mark Wielaard
2022-08-17 13:24       ` Frank Ch. Eigler
2022-08-17 21:18         ` Mark Wielaard
2022-08-17 21:33           ` Frank Ch. Eigler
2022-08-18 13:50             ` Mark Wielaard
2022-08-18 14:40               ` Simon Marchi
2022-08-21 17:41                 ` Mark Wielaard
2022-08-23 20:15                   ` Mark Wielaard
2022-08-23 22:08               ` Mark Wielaard
2022-08-24 10:05                 ` Mark Wielaard [this message]
2022-08-24 21:06                   ` Mark Wielaard

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=YwX3zyp8d6GsHlG+@wildebeest.org \
    --to=mark@klomp.org \
    --cc=overseers@sourceware.org \
    --cc=simon.marchi@polymtl.ca \
    /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).