On 2/17/22 19:16, Mark Sapiro wrote:
If you rerun hyperkitty_import with the since= option set to a date earlier that the oldest message to import, it should just work. Messages which are already in the archive (by Message-ID:) will be ignored by the import process.
Great! So valuable info. Thank you, Mark. "earlier that the oldest message" you sure mean earlier then the oldest of already archived. Or since= any date of the mbox messages to be imported. Will check the hyperkitty_import for since= option format.
Yet another question. Is it supposed to stop minutely/hourly/etc. mailman3-web cron jobs during import to avoid any collisions? Or even mailman3-web completely but probably it needs to be running. I only ask because my last import attempt on a test maillist failed with
[ERROR/MainProcess] Failed indexing 1 - 2 (retry 5/5): (1712, 'Index hyperkitty_attachment is corrupted') (pid 5841): (1712, 'Index hyperkitty_attachment is corrupted')
Optimizing cured the hyperkitty_attachment InnoDB index corruption problem but scared the sh.. out of me for a moment...
Thank you for your help, Mark.
Sanyi