On 2026-10-29 14:53:30 +0300 (+0300), Washington Odhiambo via Mailman-users wrote: [...]
2 - Rename in place via SQL
Faster, but unsupported. You would update mail_host/list_id in Core, rename the template directories, then update the HyperKitty list name and the Django mail domain.
It's easy to miss a reference, so only try this on a copy of the databases, and compare lists, rosters and archives before and after. [...]
Having done this (multiple times) in the past, I can confirm it's not for the faint of heart. I worked out the update queries on a copy of the production database, doing post-hoc database dumps and scanning them for remaining references to the old domain repeatedly until I finally tracked them all down and made sure they were covered by what I planned to run in production.
Don't forget to also rename/move files on disk related to the list you're rehoming, and of course you want to do all these things with services offline (presumably deferring inbound deliveries for the duration of the maintenance).
And it should go without saying, make sure you have good backups of everything!
-- Jeremy Stanley