On 11/25/21 10:28 AM, Mark Sapiro wrote:
On 11/24/21 10:17 PM, David Newman wrote:
On 11/24/21 2:36 PM, Mark Sapiro wrote:
To import archives run the Django admin command with arguments
hyperkitty_import -l alist@example.com /path/to/mailman2.1/archives/private/alist.mbox/alist.mbox
Good up to here, but ... hyperkitty_import not found.
This wasn't covered in the venv docs:
It is covered at https://docs.mailman3.org/en/latest/migration.html#upgrade-strategy
Your issue is probably that the Django admin command you ran is not accessing your
settings.py. You may need to doexport DJANGO_SETTINGS_MODULE=settings export PYTHONPATH=/path/to/directory/containing/settings.pybefore running the Django admin command. These can also be given as --settings and --pythonpath options to the Django admin command.
Thanks for this. After setting these variables and restarting mailman3 and mailmanweb, the mailman user still cannot find a hyperkitty_import command (neither can root, btw). Again, I installed MM3 and Django/Postorius/Hyperkitty using the venv and web docs previously referenced.
On the plus side, all lists now appear in the admin web page. However, lists created from the admin page do not appear in a site list page, even though all lists are in the same site/domain.
Finally, how to make these exports permanent? I did not see this covered in the migration doc above. This is on a Debian system where the mailman user's shell is bash. Is this simply a matter of adding environment variables in the mailman user's .bashrc file?
Thanks
dn