[MM3-users] Re: Moving existing lists to a new domain

On 2024-09-18 16:36:50 -0700 (-0700), Mark Sapiro wrote:

On 9/18/24 10:13, Jeremy Stanley wrote: [...]

...

Since all the lists for the given domain will be moving to the same unused new domain on the existing server, and can move at the same time, I suppose this could be done through (offline if necessary) backend database update queries. [...]

UPDATE mailinglist SET mail_host = 'new.domain' WHERE mail_host =
'old_domain';

[...]

UPDATE mailinglist SET list_id = CONCAT(list_name, '.', mail_host) WHERE
mail_host = 'new_domain';

For HyperKitty, similar changes need to be made to the hyperkitty_mailinglist table. The name column entries need to be changed from listname@old.domain to listname@new.domain and the list_id column entries need to be changed from listname.old.domain to listname.new.domain

Preparing to test this, I poked around the schema a bit and noticed that the domain names are also embedded as strings in the following fields:

django_mailman3_maildomain.mail_domain
django_site.domain
django_site.name
domain.mail_host

Can anyone think of any additional tables/columns which would need updating for this? I'll see if scanning a dump of the full DB content turns up anything I might be missing too. Thanks again!

-- Jeremy Stanley