Re: Process on migrating mailman
On Tue, Jan 23, 2024 at 4:22 AM Mark Labeste <marqueejen13@gmail.com> wrote:
About 500 list. Not sure how to check size of the archives.
On Thu, Jan 18, 2024 at 4:44 PM Odhiambo Washington <odhiambo@gmail.com> wrote:
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.
The archives are in the database so nothing to worry about, Now that I think about this again, after dumping and importing the database as shown above, you need to rerun the 'mailman-web migrate` once again to import any DB schema changes between the versions. Actually, just run all the options from https://docs.mailman3.org/en/latest/install/virtualenv.html#run-database-mig... .
-- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]
Just like to confirm when doing this dumping process. Nothing will change on the current mailing list?
On Tue, Jan 23, 2024 at 2:01 PM Odhiambo Washington <odhiambo@gmail.com> wrote:
On Tue, Jan 23, 2024 at 4:22 AM Mark Labeste <marqueejen13@gmail.com> wrote:
About 500 list. Not sure how to check size of the archives.
On Thu, Jan 18, 2024 at 4:44 PM Odhiambo Washington <odhiambo@gmail.com> wrote:
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.
The archives are in the database so nothing to worry about, Now that I think about this again, after dumping and importing the database as shown above, you need to rerun the 'mailman-web migrate` once again to import any DB schema changes between the versions. Actually, just run all the options from https://docs.mailman3.org/en/latest/install/virtualenv.html#run-database-mig... .
-- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]
-- Regards, mARK
Once you dump and replace DOMAIN1 with DOMAIN2, everything else should remain the same.
PS: Could you please try and not top-post? Put your replies below the ones you receive.
On Tue, Jan 23, 2024 at 9:57 AM Mark Labeste <marqueejen13@gmail.com> wrote:
Just like to confirm when doing this dumping process. Nothing will change on the current mailing list?
[snip]
Once you dump and replace DOMAIN1 with DOMAIN2 globally, everything else should remain the same.
Stop both Mailman's processes:
systemctl stop mailman3
systemctl stop mailmanweb
Assuming that Mailman core and Mailman web were using the same DB (named mailman3), dump the DB and replace DOMAIN1 with DOMAIN2 in the sump file:
mysqldump mailman3 > mailman3-DOMAIN1.sql
sed "s/DOMAIN1/DOMAIN2/g" mailman3-DOMAIN1.sql > mailman3-DOMAIN2.sql
mysql mailman3 < mailman3-DOMAIN2.sql
Run the migrations as documented in https://docs.mailman3.org/en/latest/install/virtualenv.html#run-database-mig...
Restart the processes
systemctl start mailman3
systemctl start mailmanweb
Of course, check your logs for anything strange and fix it :)
PS: Could you please try and not top-post? Put your replies below the ones you receive.
-- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]
Once you dump and replace DOMAIN1 with DOMAIN2 globally, everything else should remain the same.
Stop both Mailman's processes:
systemctl stop mailman3
systemctl stop mailmanweb
Assuming that Mailman core and Mailman web were using the same DB (named mailman3), dump the DB and replace DOMAIN1 with DOMAIN2 in the sump file:
mysqldump mailman3 > mailman3-DOMAIN1.sql
sed "s/DOMAIN1/DOMAIN2/g" mailman3-DOMAIN1.sql > mailman3-DOMAIN2.sql
mysql mailman3 < mailman3-DOMAIN2.sql
Run the migrations as documented in https://docs.mailman3.org/en/latest/install/virtualenv.html#run-database-mig...
Restart the processes
systemctl start mailman3
systemctl start mailmanweb
Of course, check your logs for anything strange and fix it :)
PS: Could you please try and not top-post? Put your replies below the ones you receive.
On Tue, Jan 23, 2024 at 3:28 PM Odhiambo Washington <odhiambo@gmail.com> wrote:
Once you dump and replace DOMAIN1 with DOMAIN2, everything else should remain the same.
PS: Could you please try and not top-post? Put your replies below the ones you receive.
On Tue, Jan 23, 2024 at 9:57 AM Mark Labeste <marqueejen13@gmail.com> wrote:
Just like to confirm when doing this dumping process. Nothing will change on the current mailing list?
[snip]
Once you dump and replace DOMAIN1 with DOMAIN2 globally, everything else should remain the same.
Stop both Mailman's processes:
systemctl stop mailman3 systemctl stop mailmanwebAssuming that Mailman core and Mailman web were using the same DB (named mailman3), dump the DB and replace DOMAIN1 with DOMAIN2 in the sump file:
mysqldump mailman3 > mailman3-DOMAIN1.sql sed "s/DOMAIN1/DOMAIN2/g" mailman3-DOMAIN1.sql > mailman3-DOMAIN2.sql mysql mailman3 < mailman3-DOMAIN2.sqlRun the migrations as documented in https://docs.mailman3.org/en/latest/install/virtualenv.html#run-database-mig...
Restart the processes
systemctl start mailman3 systemctl start mailmanwebOf course, check your logs for anything strange and fix it :)
PS: Could you please try and not top-post? Put your replies below the ones you receive.
-- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]
mysqldump seems not working. it says command not found.
Regards, mARK
participants (2)
-
Mark Labeste -
Odhiambo Washington