Migrating archives from Mailman21 to Mailman3
Dear List,
I have a question about migrating archives from Mailman21 to Mailman3: Is it possible to migrate only the archive of a list, but not the list?
Best regards, Markus
-- Markus Grandpré Universität Konstanz Kommunikations-, Informations-, Medienzentrum (KIM) Abteilung IT-Dienste Forschung, Lehre und Infrastruktur, Tel: ++49 7531 88 4342
On Tue, Sep 24, 2024 at 3:50 PM Markus Grandpré < markus.grandpre@uni-konstanz.de> wrote:
Dear List,
I have a question about migrating archives from Mailman21 to Mailman3: Is it possible to migrate only the archive of a list, but not the list?
I believe a lis_id is mandatory when migrating anything from MM21. So instead of migrating the archives, you can simply leave them where they are and give a URL to access them.
-- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]
On 9/24/24 05:49, Markus Grandpré wrote:
Dear List,
I have a question about migrating archives from Mailman21 to Mailman3: Is it possible to migrate only the archive of a list, but not the list?
Yes. There is no requirement that archives have a matching list in Mailman core.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On Tue, Sep 24, 2024 at 7:38 PM Mark Sapiro <mark@msapiro.net> wrote:
On 9/24/24 05:49, Markus Grandpré wrote:
Dear List,
I have a question about migrating archives from Mailman21 to Mailman3: Is it possible to migrate only the archive of a list, but not the list?
Yes. There is no requirement that archives have a matching list in Mailman core.
So the documentation at https://docs.mailman3.org/en/latest/migration.html needs revision as it creates the impression that a matching list needs to be there:
$ python manage.py hyperkitty_import -l foo-list@example.com
$var_prefix/archives/private/foo-list.mbox/foo-list.mbox
-- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]
On 9/24/24 12:03, Odhiambo Washington via Mailman-users wrote:
On Tue, Sep 24, 2024 at 7:38 PM Mark Sapiro <mark@msapiro.net> wrote:
Yes. There is no requirement that archives have a matching list in Mailman core.
So the documentation at https://docs.mailman3.org/en/latest/migration.html needs revision as it creates the impression that a matching list needs to be there:
$ python manage.py hyperkitty_import -l foo-list@example.com $var_prefix/archives/private/foo-list.mbox/foo-list.mbox
Are you saying that the above quoted command is what gives that
impression? I don't see that foo-list@example.com is the name of the
list for the HyperKitty archive only and
$var_prefix/archives/private/foo-list.mbox/foo-list.mbox is the MM 2.1
mbox.
If you are saying something else gives that impression, what in particular is that?
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On Tue, Sep 24, 2024 at 11:33 PM Mark Sapiro <mark@msapiro.net> wrote:
On 9/24/24 12:03, Odhiambo Washington via Mailman-users wrote:
On Tue, Sep 24, 2024 at 7:38 PM Mark Sapiro <mark@msapiro.net> wrote:
Yes. There is no requirement that archives have a matching list in Mailman core.
So the documentation at https://docs.mailman3.org/en/latest/migration.html needs revision as it creates the impression that a matching list needs to be there:
$ python manage.py hyperkitty_import -l foo-list@example.com $var_prefix/archives/private/foo-list.mbox/foo-list.mboxAre you saying that the above quoted command is what gives that impression? I don't see that
foo-list@example.comis the name of the list for the HyperKitty archive only and$var_prefix/archives/private/foo-list.mbox/foo-list.mboxis the MM 2.1 mbox.If you are saying something else gives that impression, what in particular is that?
My thinking around the above was that foo-list@example.com refers to a
Mailman list.
But now I am beginning to think that it's only a listname for HyperKitty
and the list doesn't necessarily have to exist in Mailman Core.
Is that right?
The fact that the command was referenced during the migration of an ACTUAL list is what created the impression (in my mind) that the list must also be a valid list for the Core.
-- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]
On 9/28/24 08:00, Odhiambo Washington via Mailman-users wrote:
My thinking around the above was that
foo-list@example.comrefers to a Mailman list. But now I am beginning to think that it's only a listname for HyperKitty and the list doesn't necessarily have to exist in Mailman Core. Is that right?
Yes.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
participants (3)
-
Mark Sapiro -
Markus Grandpré -
Odhiambo Washington