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