Hi all,
There are lots of threads for mm2 -> mm3 moves, but only one thread mm3 -> mm3. Some time ago, I found a post from Mark, explaining the steps, but I can't find it again.
I have created a working mm3 installation on the new host with both mailman and mail-web dbs imported. hyperkitty archive seems to in the db.
What are the next steps to complete the transfer?
rsyncing messages, lists and templates to new host
Setting up DNS CNAMES to the new server
Adapting exim to accept mails to the aliased domain
Can I keep the old listname, with the old domain name?
-What else has to be done ?
Thanks, Axel
PGP-Key: CDE74120 ☀ mobile: +49 160 7568212 computing @ chaos claudius
On 10/19/23 02:38, Axel Rau wrote:
Hi all,
There are lots of threads for mm2 -> mm3 moves, but only one thread mm3 -> mm3. Some time ago, I found a post from Mark, explaining the steps, but I can't find it again.
I have created a working mm3 installation on the new host with both mailman and mail-web dbs imported. hyperkitty archive seems to in the db.
What are the next steps to complete the transfer?
- rsyncing messages, lists and templates to new host
You may want to add archives/prototype to that. Also note that the contents of the messages/ directory should correspond to the entries in the message table in the mailman db.
Setting up DNS CNAMES to the new server
Adapting exim to accept mails to the aliased domain
Can I keep the old listname, with the old domain name?
As long as mail to the list at that domain gets delivered to the new server. Note that in DNS if the domain has an MX record it must point to a domain with and A record and if there is no MX record, there must be an A record. CNAMEs won't do for mail delivery.
-What else has to be done ?
I think that's it.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
participants (2)
-
Axel Rau
-
Mark Sapiro