2015-06-03 11:17 GMT+03:00 Aurelien Bompard <aurelien@bompard.org>:

If the first URL does not match, it means that HyperKitty is not activated in the virtualhost for 127.0.0.1. You should get a message in HyperKitty's logs stating that the connection was refused because the IP address is not allowed. You have two options:

• activate HyperKitty for 127.0.0.1
• in HyperKitty's settings file (production.py), edit the MAILMAN_ARCHIVER_FROM variable to allow you local IP. This IP address must not change.

Thank you, Aurelian. Now I'm figured all these out.

The first option - to activate Hyperkitty on 127.0.0.1 is not good opportunity for me because I have shared host and would not have Mailman 3 archive/manager on every domain I have there instead of its actual content. :)

Below is the instruction how you would configure Mailman3 just for one virtual host of your server.

1. Put content of deployment/apache.conf into the virtualhost section of your Mailman 3 archive/manager domain - every line excluding the following 4 ones:

WSGISocketPrefix run/wsgi WSGIRestrictStdout On WSGIRestrictSignal Off WSGIPythonOptimize 1

You must put them outside of any of your virtualhost section.

2. Edit your deployment/mailman-hyperkitty.cfg file and set base_url: http://yourvirtualhostdomain.tld/archives

3. Add to your mailman_web/settings_local.py the ip address of your virtual host:

MAILMAN_ARCHIVER_FROM = ('ip.ip.ip.ip')

I hope this will help someone.

Everybody have a great weekend, Danil