Julian Kippels writes:
I want to move all my lists to another server.
This is conceptually straightforward as long as you keep the same posting addresses. Just move all the "files" (you probably want to do a dump and restore of the RDMBS rather than rsyncing the DB files). You should move *all* of the files in /etc/mailman3, not just the three Odhiambo listed. You probably have WGSI configuration files (eg, gunicorn.conf, uwsgi.ini), and may have include files for mailman.cfg and settings.py, as well as various localizations such as template files. You need to clean up all of the files related to mailman.cfg and settings.py for the domains.
That may not work as well as you would like if you are using distro packages rather than a virtualenv install from source, because unless you're a distro wizard you likely won't get the same versions of everything. But it's a pretty good bet.
While I am doing that, I also want to change all lists from listname@domain.tld to listname@lists.domain.tld
This is not easy in general. In principle, you "should" be able to just change the mail host entry in the database. You probably should *not* change the list ID entry. However, it is quite frequent to configure lists as subscribers to other lists. (I think I've seen them as other kinds of member, such as owner, as well.) This is done using the list's address as a string, not as a MailingList object, so you would need to change those by hand (unless you maintain aliases on domain.tld, but I think that's what you want to avoid).
In Mailman 2, there were a number of other possibilities, such as "sibling lists" (alternative lists to check for membership when a list is "members-only"). I don't recall which of these, if any, are implemented in Mailman 3, and I definitely don't recall if they are implemented via MailingList object, list ID, or by posting address.
Finally there are a couple of obscure options that use regexps to filter addresses. I don't think lists are among the use cases, but I can't promise.
How would I best go about this?
That depends on your users. See below for an example.
Will I have issues with the archives of the lists when the domain changes?
Is the archive server going to move as well? That's likely to annoy users who have bookmarks. (This is one reason why a lot of people like to have lists.domain.tld and archive.domain.tld.)
If you're not using HyperKitty, all bets are off -- you need to discuss with the maintainers of the archive software you use. For HyperKitty, I don't recall how it identifies lists. If it uses list ID, and you don't change it, you may be home free.
Otherwise, it's likely users will perceive a discontinuity post-move vs pre-move, such as broken threads. I'm not sure how HyperKitty handles threads that are continued on a different list.
-- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan