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.
Yes.
For the mailing list, the only changes needed are to the mailinglist
table; A query like
```
UPDATE mailinglist SET mail_host = 'new.domain' WHERE mail_host =
'old_domain';
```
would do, but this leaves the question of list_id. According to RFC
2919, section 4, the list_id should not change, but this is problematic
in that if it isn't changed, a Postorius URL like
https://example.com/mailman3/lists/list_name@new.domain will retrieve
the list, but https://example.com/mailman3/lists/list_name.new.domain
will not work. It would need to be
https://example.com/mailman3/lists/list_name.old.domain so to reduce
confusion, it may be better to update the list_id values
A query like the following after the above should do it
```
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`
--
Mark Sapiro <m...@msapiro.net> The highway is for gamblers,
San Francisco Bay Area, California better use your sense - B. Dylan
_______________________________________________
Mailman-users mailing list -- mailman-users@mailman3.org
To unsubscribe send an email to mailman-users-le...@mailman3.org
https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/
Archived at:
https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message/WPJK6HH3IIHO5P6B6IBAW5M5OFZT27TF/
This message sent to arch...@mail-archive.com
