Thank you Mark, this got me on the right track. But I still think this not at all clear when reading the docs.

My system is in a venv. I had to run these commands:

mailman-web hyperkitty_import --since=01.01.2022 -l mylist@mydomain my-mbox-file

mailman-web update_index_one_list mylist@mydomain Where is it stated that in this situation I have to run mailman-web instead of django-admin?

Thanks anyway, problem solved.

Am Donnerstag, 8. Dezember 2022, 17:51:58 CET schrieb Mark Sapiro:

On 12/7/22 05:57, Eggert Ehmke wrote:

...

I was able to export the archive of my old mm3 installation in hyperkitty. However, I seem to be blind when looking for hyperkitty_import in the documentation. Where to start?

There is documentation at <https://docs.mailman3.org/projects/hyperkitty/en/latest/development.html#im porting-the-current-archives> and also at <https://docs.mailman3.org/en/latest/migration.html#upgrade-strategy>. You can also run django-admin hyperkitty_import --help. The docs refer to importing messages from MM 2.1, but you can import messages from any unix like mbox file.

Note in the above, django-admin is the command you use to invoke Django's management which may be django-admin, manage.py, mailman-web or something else depending on how Mailman is installed.

Eggert Ehmke writes:

Where is it stated that in this situation I have to run mailman-web instead of django-admin?

If you have mailman-web in your venv, that's what to run.

It's hard to give a rule for the others; in fact I suspect both will usually work (they all end up being equivalent, running the same code from Django and Mailman).

We developed mailman-web to try to make that choice obvious (and it's the default in most of the install and configuration documentation). But lots of people have older installations that don't have mailman-web, and others are following older Mailman documentation or third-party documentation.

Steve