Christian Schneider writes: > All this hustle to accommodate users decomissioning a list and > after three days wanting it back... :-/
I'm curious how often you (or anybody) sees this request. FWIW there are 3 issues related to per-list backups. It's a plausible feature (lots of potential applications), so I just added the below to Mailman's 2026 GSoC page, so maybe we'll get an intern to do it. == Per-list backup == In Mailman 2, the list configurations were stored in list-specific structures as Python ''pickles''. Backup of a single list was just a matter of copying the pickle file. Currently there is no way to extract and restore the configuration and membership of a single list from a Mailman 3 installation. This project would involve picking a format such as a Python pickle or a JSON object, extracting the list-specific data from the backing database, and storing it to a file, as well as reversing the process. Tags: ''core'', ''postorius'' === Requirements === * Level: medium * Estimated effort: 175 hours === Mentors === * Stephen J. Turnbull -- 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://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ Archived at: https://lists.mailman3.org/archives/list/[email protected]/message/UDTYT2JZPVNFVUDWDYNICMAL3KIELBUN/ This message sent to [email protected]
