On Thu, Jan 26, 2023 at 3:58 PM Jeffrey Westgate < jeffrey.westg...@arkansas.gov> wrote:
> Greetings all - > > My current build is running Mailman version: 2.1.20, on a > long-in-the-tooth Scientific Linux release 7.9 (Nitrogen), with sendmail > > I'd like to go RHEL9, and Mailman 3.3.8 (Tom Sawyer), with postfix, on a > new parallel VM - > plan is to build a parallel server, same hostname, different IP, migrate > all data/archives and billing info (we have that scripted), then do a dns > change to point to the new IP after testing. > > Are there any means of scripted migration from old to new? > There is a host on which I had several lists. A number of lists were related to one domain (domain1.name) and one list was on a different domain (domain2.name) After I had completed the whole process of installing MM3 (in a virtualenv), I created two sites under /admin. After having ensured that the old (MM2) directories were readable by the MM3 user, I did this (from the virtualenv): #1 - Created the lists in MM3 for m in list1 list2 list2 listN; do /opt/mailman/mm/venv/bin/mailman create $m...@domain1.name; done # for the lists that shared a domain /opt/mailman/mm/venv/bin/mailman create l...@domain2.name # For the other list #2 - Imported the list configs into MM3 for m in list1 list2 list2 listN; do /opt/mailman/mm/venv/bin/mailman import21 $m...@domain1.name /var/list/lists/$m/config.pck; done /opt/mailman/mm/venv/bin/mailman import21 l...@domain2.name /var/list/lists/LIST/config.pck #3 - Imported the archives in MM3 for m in list1 list2 list2 listN; do /opt/mailman/mm/bin/django-admin hyperkitty_import -l $m...@domain1.name /var/list/archives/private/$m.mbox/$m.mbox; done /opt/mailman/mm/bin/django-admin hyperkitty_import -l l...@domain2.name /var/list/archives/private/LIST.mbox/LIST.mbox #4 - Index the lists with '/opt/mailman/mm/bin/django-admin update_index_one_list' LIST@DOMAIN You could script that process, no? PS: On another site, I encountered issues with the mbox from MM2 having some characters that the import process did not like. It was also kinda related to MySQL. I am not sure if the same would affect PostgreSQL, but I am mentioning just so that you know you need to watch the archive import process keenly, as that is perhaps the most critical part of the migration - archives! > Can I go from 2.1.20 direct to 3.3.8 - or do I need to go to 2.1.39 as an > intermediate first? > I don't think it is necessary, because I haven't seen any documentation saying so. Why did you not update your 2.1.20 despite the security patches/enhancements? Or it's a case of if it ain'r br0ken, don't touch it? :-) It's a service we provide, and we like to keep the our level of interaction > to a minimum, so 2.1.20 was the first built "I" did back when RHEL7/SL7 was > in it's early days. Going latest would fill that mold for us for a while. > Python2.7 was EoL-ed and some guy from Mars might just ask ChatGPT a question that might lead to that "for a while" giving you nightmares! > I'm currently looking at the wiki.list.org, but am having troubles > locating Mailman3. version Site Admin doc - they seem to be v2.1 - I could > be missing them. I'm old. > What are you looking for when you say "Site Admin doc"? Most of the things you are looking for can be found on this link below: https://docs.mailman3.org/en/latest/install/virtualenv.html -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) ------------------------------------------------------ Mailman-Users mailing list -- mailman-users@python.org To unsubscribe send an email to mailman-users-le...@python.org https://mail.python.org/mailman3/lists/mailman-users.python.org/ Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/ https://mail.python.org/archives/list/mailman-users@python.org/
