Steven Jones via Mailman-Users writes: > How would this be done?
See Mark's message. > I assume take Mailman2 down for a day or 2, standup Mailman3 and > migrate the lists but this seems a high risk undertaking. I don't think there's much risk. You just have to be careful about the potential race between creation of each mailing list (when the MTA considers it routable) and the migration of the subscriber roster (when a post will be distributed to the intended recipients). Even if an incoming post managed to sqsueeze through that gap, it would still be in the archive as long as archiving is enabled. I don't know if Mark's script handles that (I suppose it would, there are a couple of ways to do it). I've done such migrations on a dedicated Mailman host with 20,000 lists and the same order of magnitude of users, and on another very complex system with 5000 lists and 100,000+ users, with zero list downtime and no problems with Mailman. (The "complex" system had a bunch of problems, but Mailman (2 or 3) caused none of them.) Archives are much more time-consuming if you enable full-text search. (That 20k list host's archives took 3 weeks to be fully indexed! Of course you can keep the Mailman 2 archives available until your Mailman 3 (HyperKitty) archives are fully indexed. -- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan ------------------------------------------------------ Mailman-Users mailing list -- [email protected] To unsubscribe send an email to [email protected] 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/[email protected]/ https://mail.python.org/archives/list/[email protected]/ Member address: [email protected]
