We're getting closer to migrating from Mailman 2 to Mailman 3. In preparation, I want to get new servers built ready to accept the migrated data from our old MM2 servers before we shut them down.

So, the new servers will be something like "new-lists.example.com" to complement the existing "lists.example.com" servers. When we are ready to do the migration, we'll rename the MM2 servers to "old-lists" and rename the MM3 servers to "lists" and then migrate the data.

Looking at the settings in the Django admin interface, I *thought* I had figure out how best to do this:

• Under /admin/sites/site/, click on the existing domain name and change it to match the correct FQDN.
• Under /admin/django_mailman3/maildomain/, click on the exist mail domain and change the mail domain to match the correct FQDN.

However, although the above works, if I then go back to the *Mailman* interface and go to /mailman3/domains/, the web interface recreates a domain for the original domain name that was in place when the server was created, i.e. we end up with "lists" and "new-lists".

We've tried deleting that "new-lists" domain, rebooting and trying again but "new-lists" keeps on being created again.

What am I overlooking here? Is there a better/approved way to achieve what we want to achieve?

Thanks.

Philip