Issues with importing archives from a particular list
Hello,
We are trying to import archives from Mailman2 to Mailman3. For a particular list, it is not importing all of the messages. We can see that Mailman2 has archives from 2015 to 2022. But, it only imports messages from 2018 to 2022 to the Mailman3 server. It was not giving any errors while importing.
All other lists are imported successfully.
Any idea what was causing the problem?
Kind regards, Prasanth
On 1/13/22 4:33 AM, Prasanth Nair wrote:
Hello,
We are trying to import archives from Mailman2 to Mailman3. For a particular list, it is not importing all of the messages. We can see that Mailman2 has archives from 2015 to 2022. But, it only imports messages from 2018 to 2022 to the Mailman3 server. It was not giving any errors while importing.
The problem list probably already had an archived message from 2018. If you don't specify a --since= date for hyperkitty_import, it only imports messages newer than the newest existing message in the archive.
You can run it again with, e.g., --since=2000-01-01. It won't reimport the messages already imported because of duplicate message ids.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On Thu, 13 Jan 2022 at 18:01, Mark Sapiro <mark@msapiro.net> wrote:
On 1/13/22 4:33 AM, Prasanth Nair wrote:
Hello,
We are trying to import archives from Mailman2 to Mailman3. For a particular list, it is not importing all of the messages. We can see that Mailman2 has archives from 2015 to 2022. But, it only imports messages from 2018 to 2022 to the Mailman3 server. It was not giving any errors while importing.
The problem list probably already had an archived message from 2018. If you don't specify a --since= date for hyperkitty_import, it only imports messages newer than the newest existing message in the archive.
You can run it again with, e.g., --since=2000-01-01. It won't reimport the messages already imported because of duplicate message ids.
Thank you, Mark, for your reply.
It turned out that this wasn't an issue with any part of the Mailman 3 suite. Unbeknownst to Prasanth, the affected list had previously been migrated from a different server in 2018 but, for some reason, the mbox file was not copied over - just the pipermail archive directory was. That explains the split between the pipermail archives and the mbox file.
Thankfully, the original server still had the older mbox file so we've now been able to import all of the messages into HyperKitty.
Apologies for the noise.
Regards
Philip
participants (3)
-
Mark Sapiro -
Philip Colmer -
Prasanth Nair