Thank you kindly, Mark, for pointing me in the right direction on multiple questions so far! I'll dig into the import command and hopefully that resolves most of the chaos if the client decides to agree with the decision to move to Mailman 3
Thomas
-----Original Message----- From: Mark Sapiro <mark@msapiro.net> Sent: Saturday, June 24, 2023 6:41 PM To: mailman-users@mailman3.org Subject: [MM3-users] Re: Importing MBOX from custom listserv to MM3?
On 6/24/23 3:26 PM, Thomas Ward wrote:
We are looking at moving from a home grown listserv system at a client to potentially MailMan3 for the lists platform instead.
We have historic thread data from the homegrown systems in mbox form. Is there a way to import that into MM3 for indexing in the archiver there so we dont need to keep the (literally massive) MBOX file?
That's what the django admin hyperkitty_import command is for.
You can check the mbox for anomalies that might cause issues with the scripts at https://gitlab.com/mailman/hyperkitty/-/tree/master/hyperkitty/contrib.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Mailman-users mailing list -- mailman-users@mailman3.org To unsubscribe send an email to mailman-users-leave@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message/...
This message sent to teward@thomas-ward.net