user/dev discussion of public-inbox itself
 help / color / mirror / code / Atom feed
From: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
To: Eric Wong <e@yhbt.net>
Cc: meta@public-inbox.org
Subject: setting up mailman2 and public-inbox
Date: Tue, 10 Mar 2020 00:07:21 +0000	[thread overview]
Message-ID: <CAPweEDy19mMYdSk3_7Oper3=+ZidgppELChhBE4HX8fXiE2rGA@mail.gmail.com> (raw)
In-Reply-To: <20200204205541.GB27797@dcvr>

eric, hi,

we're having difficulty understanding how to deploy public-inbox in a
way that very simply and as a top and only priority records email in a
public inbox, for the purposes of having it in a git repository, when
that email is coming in via exim4 and going into mailman2.

this really cannot be difficult.

we do not want to replace mailman2: its front-end, the subscription
capabilities, the user management are perfect and protect against
spammers, keeping the list clean.

we do not want to replace the pipermail archives at this point,
although that may be something we could consider at a later date.

the *only* thing that we want public-inbox for - right now - is its
ability to store the list email - *after* processing and acceptance by
mailman - in a git-backed repository, so that people in offline
situations have full and complete access to the archives.

how *exactly* do we do that one thing and one thing only?

(basically, if public-inbox accepted mbox format we could do what we
need, straight away.  the conversion process and the extra CPU time is
not a problem, because we already have to accept that overhead on
conversion, and the lists each month are not that big: 700 messages or
so).

are we missing something really simple?

if we subscribe a local user on the server (inbox@libre-riscv.org) to
the actual list, then configure that local account to have mail
delivered Maildir format, would that do the trick?

tia,

l.

  parent reply	other threads:[~2020-03-10  0:07 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-04 18:42 setting up mailman-to-atom-converter then atom-to-public-inbox Luke Kenneth Casson Leighton
2020-02-04 20:55 ` Eric Wong
2020-02-04 21:49   ` Luke Kenneth Casson Leighton
2020-02-04 22:14     ` Eric Wong
     [not found]       ` <CAPweEDy1qTK93pXDKdbT-HqJV184fH7x0hqqJYDTMv_nxvoKqQ@mail.gmail.com>
2020-02-05  0:10         ` Eric Wong
     [not found]           ` <CAPweEDyYA+38B4uc+stMpZ9q6CrHaaAAkkorCuH4ONHmhBXbXg@mail.gmail.com>
2020-02-05  0:43             ` Eric Wong
2020-02-05  1:02               ` Kyle Meyer
2020-02-05  1:04                 ` Eric Wong
2020-03-10  0:07   ` Luke Kenneth Casson Leighton [this message]
2020-03-11 10:33     ` setting up mailman2 and public-inbox Eric Wong
2020-03-11 11:58       ` Luke Kenneth Casson Leighton
2020-03-11 12:47         ` Luke Kenneth Casson Leighton

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='CAPweEDy19mMYdSk3_7Oper3=+ZidgppELChhBE4HX8fXiE2rGA@mail.gmail.com' \
    --to=lkcl@lkcl.net \
    --cc=e@yhbt.net \
    --cc=meta@public-inbox.org \
    --subject='Re: setting up mailman2 and public-inbox' \
    /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

Code repositories for project(s) associated with this inbox:

	https://80x24.org/public-inbox.git

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).