Problems configuring hyperkitty
I am having another go at installing mailman3 - I seem to have mailman3 & postorius working - although basic testing, much more needed to confirm that I understand it. I want to get hyperkitty working before I start full testing.
I am running Debian 12 - Bookworm and have installed the Debian packages. The database is Mysql. This is not a virtualenv setup. There is no documentation in the hyperkitty package so I am following:
https://docs.mailman3.org/projects/hyperkitty/en/latest/install.html
I read the following:
"The database can be created with the following command:
django-admin migrate --pythonpath example_project --settings settings "
I assume that that will create some database tables. Hopefully this will have been done by installing package python3-mailman-hyperkitty.
• What database & tables will that be ? It would be really useful to be told so that I can check.
• The config file is: /etc/mailman3/mailman-hyperkitty.cfg This does not contain any comment about databases. Where does hyperkitty get its database parameters from ?
• I have several different maildomains each with several lists. Some lists in different domains have the same name. Do I need a different example_project/settings.py for each domain, if so what changes ?
One of the next things that I will need to do is to import archives from mailman2. How does the command below change for the different domains ?
django-admin hyperkitty_import --pythonpath example_project --settings settings -l ADDRESS mbox_file [mbox_file ...]
Is there some better documentation that I have failed to find ?
Regards
-- Alain Williams Linux/GNU Consultant - Mail systems, Web sites, Networking, Programmer, IT Lecturer. +44 (0) 787 668 0256 https://www.phcomp.co.uk/ Parliament Hill Computers. Registration Information: https://www.phcomp.co.uk/Contact.html #include <std_disclaimer.h>
On 11/18/24 09:29, Alain D D Williams wrote:
I am running Debian 12 - Bookworm and have installed the Debian packages. The database is Mysql. This is not a virtualenv setup. There is no documentation in the hyperkitty package so I am following:
https://docs.mailman3.org/projects/hyperkitty/en/latest/install.html
The primary support resource for Debian packages is Debian. See https://wiki.list.org/x/12812344
I read the following:
"The database can be created with the following command:
django-admin migrate --pythonpath example_project --settings settings "
I assume that that will create some database tables. Hopefully this will have been done by installing package python3-mailman-hyperkitty.
• What database & tables will that be ? It would be really useful to be told so that I can check.
The database is configured in the DATABASES setting in your Django
settings. The HyperKitty tables all have names beginning with hyperkitty_.
• The config file is: /etc/mailman3/mailman-hyperkitty.cfg This does not contain any comment about databases. Where does hyperkitty get its database parameters from ?
Django, see above.
• I have several different maildomains each with several lists. Some lists in different domains have the same name. Do I need a different example_project/settings.py for each domain, if so what changes ?
I can't really speak to Debian, but you should be using the Django settings provided as part of Django's mailman-web package, not the ones in hyperkitty/example_project/settings.py as those don't include settings necessary for Postorius.
One of the next things that I will need to do is to import archives from mailman2. How does the command below change for the different domains ?
django-admin hyperkitty_import --pythonpath example_project --settings settings -l ADDRESS mbox_file [mbox_file ...]
In the -l ADDRESS argument the ADDRESS is the fully qualified list
address and includes the domain.
Is there some better documentation that I have failed to find ?
Ask Debian.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Alain D D Williams wrote:
I assume that that will create some database tables. Hopefully this will have been done by installing package python3-mailman-hyperkitty.
You'll need mailman3, mailman3-web and python3-mailman-hyperkitty installed (or mailman3-full, which includes those three).
• What database & tables will that be ? It would be really useful to be told so that I can check.
+-----------------------------------+ | Tables_in_mailman3web | +-----------------------------------+ | account_emailaddress | | account_emailconfirmation | | auth_group | | auth_group_permissions | | auth_permission | | auth_user | | auth_user_groups | | auth_user_user_permissions | | django_admin_log | | django_content_type | | django_mailman3_maildomain | | django_mailman3_profile | | django_migrations | | django_q_ormq | | django_q_schedule | | django_q_task | | django_session | | django_site | | hyperkitty_attachment | | hyperkitty_email | | hyperkitty_favorite | | hyperkitty_lastview | | hyperkitty_mailinglist | | hyperkitty_mailinglist_moderators | | hyperkitty_mailinglist_owners | | hyperkitty_profile | | hyperkitty_sender | | hyperkitty_tag | | hyperkitty_tagging | | hyperkitty_thread | | hyperkitty_threadcategory | | hyperkitty_vote | | postorius_emailtemplate | | socialaccount_socialaccount | | socialaccount_socialapp | | socialaccount_socialapp_sites | | socialaccount_socialtoken | +-----------------------------------+
• I have several different maildomains each with several lists.
I think (!) you'll have to add each mail domain in Django, i.e. <http://yourhost.example/mailman3/admin/>, section "Django Mailman 3", "Mail domains".
Some lists in different domains have the same name.
Doesn't matter, as the list name for all parts of Mailman3 is "listname@domain.example", i.e. including the domain.
One of the next things that I will need to do is to import archives from mailman2. How does the command below change for the different domains ?
django-admin hyperkitty_import --pythonpath example_project --settings settings -l ADDRESS mbox_file [mbox_file ...]
AFAIS you'll have to use "/usr/share/mailman3-web/manage.py" instead of "django-admin".
For me, that command has worked:
| python3 /usr/share/mailman3-web/manage.py hyperkitty_import -l listname@domain.example /path/to/listname.mbox
You'll have to do that for every list, regardless of domain.
Is there some better documentation that I have failed to find ?
Not that I know of.
Most is - more or less - documented, but it's not easy to apply the documentation to a Debian installation. It was a bumpy ride, but not really that problematic, as I remember; some googling and try and error was involved. ;)
-thh
participants (3)
-
Alain D D Williams -
Mark Sapiro -
Thomas Hochstein