From: "Frank Ch. Eigler" <fche@elastic.org>
To: Mark Wielaard <mark@klomp.org>
Cc: Overseers mailing list <overseers@sourceware.org>,
Simon Marchi <simon.marchi@polymtl.ca>
Subject: Re: inbox.sourceware.org experiment
Date: Wed, 17 Aug 2022 17:33:40 -0400 [thread overview]
Message-ID: <Yv1etC4DBs+v6RD1@elastic.org> (raw)
In-Reply-To: <Yv1bK/fAu86QXP98@wildebeest.org>
Hi -
> [...]
> > Yes, understood that the extra indexing can do extra searches. My
> > question was about utility/need for this.
>
> The use seems obvious to me for anybody using the web based archives
> to generate tailored message/mbox results, specifically date ranged
> searches seem pretty mandatory since otherwise you essentially just
> need to keep clicking, next, next, next.
I was under the impression that your main interest in p-i was the easy
addressability and availability of raw emails, for use such as with
git-am. Are there other users pining for this kind of thing?
> But also to get specific messages based on author or subject. On
> specific use case for public-inbox is to not have to be subscribed
> to a list to read it [...]
You are expecting people to use the xapian query language for this
stuff? Mailman offers that style of click-click browsing already.
> [...]
> So this is before mailman sees the message, so we do need to do a
> spam-check.
No, postfix already spam checks everything upon receipt, before delivery.
> And I think postfix sets ORIGINAL_RECIPIENT already, we just need to
> make sure it is one of the addresses for a list in the config.
This shouldn't be something that we need to write code to do, if it needs
to be done at all.
> But what generates /etc/mailman/aliases itself? Can we hook into that
> to trigger generation of this aliases-inbox file? Otherwise if we add
> a new mailman list it won't work.
It must be some mailman administrative script. Just crontab another
one.
> And do we need to update/regenerate
> /etc/aliases.db and/or /etc/mailman/aliases.db ?
The proposal is to not touch /etc/aliases* NOR /etc/mailman/aliases*.
The proposal is to generate a new file like
/etc/postfix/mailman-inbox-aliases from /etc/mailman/aliases. That
new file would be the one postfix would read. It could be texthash:
rather than hash: so postmap would not even be necessary for updates.
That depends on whether the relevant alias-expansion postfix process
is short- or long-lived.
- FChE
next prev parent reply other threads:[~2022-08-17 21:33 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 [this message]
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
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=Yv1etC4DBs+v6RD1@elastic.org \
--to=fche@elastic.org \
--cc=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).