On 10/5/19 11:30 AM, Mark Dadgar wrote:
Running the commands as the correct user solved my issues. Specially, I ran the import21 command as the “list” user (created by the debian/ubuntu package) and the hyperkitty import command as the “www-data” user. I had to add login shells to the passwd entries for those users to make it happen as they get installed with nologin.
You could just run, e.g., sudo -u list bin/mailman import21 ... which
will work even if 'list' can't log in.
I imported a 24G archive inbox and something went wrong along the way - the archives for many months consist of just a single identical thread. Re-running the import results in the following in just a few seconds: ... Any thoughts on how I can re-run the full import to make sure that all the archives are present?
As far as reimporting the entire archive, you need the --since option. As it says in hyperkitty_import --help
--since SINCE only import emails later than this date. Defaults to the date of the newest message in the existing archive if any.
If you run hyperkitty_import --since=1990-01-01, that should do it.
As far as "the archives for many months consist of just a single identical thread", were there error messages when you ran the initial import? Were there issues in the imported mbox that you have corrected? Mailman 2.1's bin/cleanarch can help identify unescaped 'From ' lines that cause problems.
If unescaped 'From ' lines is the issue and you have fixed them, rerunning the import should import the messages correctly, but it won't delete the bogus threads. You can delete these threads manually in HyperKitty if you are logged in as a Django superuser.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan