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]