On Thu, Jan 18, 2024 at 8:49 AM Mark Labeste <marqueejen13@gmail.com> wrote:
Any suggestion on how to migrate mailing list and archirve with diffirent server and domain. For the mailing list from sample.domain1.example.com to sample.domain2.example.com
Old Mailing list Mailman Core Version GNU Mailman 3.3.5 (Tom Sawyer) Mailman Core API Version 3.1 Mailman Core Python Version 3.6.8 (default, Sep 26 2019, 11:57:09) [GCC 4.8.5 20150623 (Red Hat 4.8.5-39)] Domain Domain1.example.com
New Mailing list Mailman Core Version GNU Mailman 3.3.9 (Tom Sawyer) Mailman Core API Version 3.1 Mailman Core Python Version 3.9.18 (main, Sep 22 2023, 17:58:34) [GCC 8.5.0 20210514 (Red Hat 8.5.0-20)] Domain domain2.example.com
How many lists? How big are the archives?
Looking at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/M..., it seems like it's not a trivial exercise.
However, I am wondering about the consequences of:
- dumping the DBs and doing 's/DOMAIN1/DOMAIN2/g' in the dumps, then re-importing
- editing settings.py and webserver config to reflect the DOMAIN2
- reconfiguring your MTA to handle list mails using the DOMAIN2
I am imagining a virtualenv type of installation. Is there somewhere in the data where the DOMAIN1 is hardcoded in a way that it cannot be replaced by a text editor? @Mark Sapiro <mark@msapiro.net> ?
-- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]