From: Eric Wong <e@80x24.org>
To: Ali Alnubani <alialnu@mellanox.com>
Cc: meta@public-inbox.org
Subject: Re: mailman mbox migration
Date: Wed, 13 Feb 2019 22:31:47 +0000 [thread overview]
Message-ID: <20190213223147.gkutd24zxjpmmj43@dcvr> (raw)
In-Reply-To: <VI1PR05MB4269904C05E14B769AEA5EBBD7660@VI1PR05MB4269.eurprd05.prod.outlook.com>
Ali Alnubani <alialnu@mellanox.com> wrote:
> Hi,
>
> Hope this is the right place to post this.
Of course :>
> I'm trying to migrate archives from a Mailman instance (v2.1.15). The format of the archives is mbox format.
For Mailman, Konstantin posted some scripts he used for kernel.org + Mailman
the other day:
https://git.kernel.org/pub/scm/linux/kernel/git/mricon/korg-helpers.git
Specifically:
https://git.kernel.org/pub/scm/linux/kernel/git/mricon/korg-helpers.git/tree/list-archive-maker.py
> How do you suggest I do that? It seems that public-inbox only supports maildir format. Do I need to convert my mbox files to maildir to be able to import them?
> Or is there an easier way to achieve this (i.e. mbox support from public-inbox)?
For regular mboxrd and mboxo (not mangled by Mailman), you can
look into adapting scripts/import_vger_from_mbox
Apparently, I did add support for importing mboxrd/mboxo formats
in the PublicInbox::InboxWritable::import_mbox subroutine (which
is used by import_vger_from_mbox).
mboxcl isn't supported, yet (and I've seen some really scary
mboxcl with multiple Content-Length headers, and >From escaping
to boot; so I'm not sure if that's a route I want to take...)
next prev parent reply other threads:[~2019-02-13 22:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-13 14:48 mailman mbox migration Ali Alnubani
2019-02-13 22:31 ` Eric Wong [this message]
2019-03-21 13:23 ` Ali Alnubani
2019-03-21 16:05 ` 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=20190213223147.gkutd24zxjpmmj43@dcvr \
--to=e@80x24.org \
--cc=alialnu@mellanox.com \
--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).