I installed mailman3 in a virtualenv following this guide:
https://docs.mailman3.org/en/latest/install/virtualenv.html[1] The mailinglists work very good. However, I did not manage to set up hyperkitty archiving. Archiving is enabled in mailman.cfg. I can call the Archive site from my configuration page, but it is empty.
In my /opt/mailman/mm/var/logs/mailman.log file I find error messages like:
HyperKitty failure on http://localhost/mailman/hyperkitty/api/mailman/archive: The requested URL was not found on this server.
Indeed I cannot access that url using curl. Do I have to set up a separate apache vhost? The documentation is not clear about this, or I missed it.
My external visible url is https://lists.[2]<tld>_/mailman3/mailman3/lists/_
[1] https://docs.mailman3.org/en/latest/install/virtualenv.html [2] https://lists.ftv-spandau.de/mailman3/mailman3/lists/
On 3/9/22 07:13, Eggert Ehmke wrote:
I installed mailman3 in a virtualenv following this guide:
https://docs.mailman3.org/en/latest/install/virtualenv.html[1] The mailinglists work very good. However, I did not manage to set up hyperkitty archiving. Archiving is enabled in mailman.cfg. I can call the Archive site from my configuration page, but it is empty.
In my /opt/mailman/mm/var/logs/mailman.log file I find error messages like:
HyperKitty failure on http://localhost/mailman/hyperkitty/api/mailman/archive: The requested URL was not found on this server.
Your setting in mailman-hyperkitty.cfg for base_url is
base_url: http://localhost/mailman/hyperkitty/
It needs to be the base URL for accessing hyperkitty, possibly
base_url: http://localhost/mailman3/hyperkitty/
or whatever you use to access hyperkitty from a web browser.
Whatever it is, <base_url>/api should return a page of API documentation.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
So I have to use the external url via https?
I can access the address https://lists.[1]<tld>_/mailman3/archives/api/_
so I set: (<tld> is my existing domain)
base_url: https://lists.<tld>/mailman3/archives Now I get this in the mailman.log:
Mar 14 19:40:21 2022 (166928) ACCEPT: <12973151.uLZWGnKmhe@wookie> Mar 14 19:40:21 2022 (166932) HyperKitty failure on https://lists.<tld>/mailman3/archives/ api/mailman/urls: <html><title>Forbidden</title><body> <h1>Access is forbidden</h1><p>Please check the IP addresses assigned to MAILMAN_ARCHIVER_FROM in the settings file. </p></body></html> (403) In my settings I have my local IP and 127.0.0.1 and ::1. What should I set there?
Am Montag, 14. März 2022, 18:48:51 CET schrieb Mark Sapiro:
On 3/9/22 07:13, Eggert Ehmke wrote:
I installed mailman3 in a virtualenv following this guide:
https://docs.mailman3.org/en/latest/install/virtualenv.html[1] The mailinglists work very good. However, I did not manage to set up hyperkitty archiving. Archiving is enabled in mailman.cfg. I can call the Archive site from my configuration page, but it is empty.
In my /opt/mailman/mm/var/logs/mailman.log file I find error messages like:
HyperKitty failure on http://localhost/mailman/hyperkitty/api/mailman/archive: The requested URL was not found on this server.
Your setting in mailman-hyperkitty.cfg for base_url is
base_url: http://localhost/mailman/hyperkitty/
It needs to be the base URL for accessing hyperkitty, possibly
base_url: http://localhost/mailman3/hyperkitty/
or whatever you use to access hyperkitty from a web browser.
Whatever it is,
<base_url>/apishould return a page of API documentation.
On 3/14/22 12:24, Eggert Ehmke wrote:
So I have to use the external url via https?
I can access the address https://lists.[1]<tld>_/mailman3/archives/api/_
so I set: (<tld> is my existing domain)
base_url: https://lists.<tld>/mailman3/archives Now I get this in the mailman.log:
Mar 14 19:40:21 2022 (166928) ACCEPT: <12973151.uLZWGnKmhe@wookie> Mar 14 19:40:21 2022 (166932) HyperKitty failure on https://lists.<tld>/mailman3/archives/ api/mailman/urls: <html><title>Forbidden</title><body> <h1>Access is forbidden</h1><p>Please check the IP addresses assigned to MAILMAN_ARCHIVER_FROM in the settings file. </p></body></html> (403) In my settings I have my local IP and 127.0.0.1 and ::1. What should I set there?
Is whatever is proxying to Django forwarding the IP and are you sure it matches the "my local IP" you set?
You might instead try setting base_url to http://localhost:8000/mailman3/archives/ or more likely http://localhost:8000/archives/ (I.e. whatever your webserver proxies the https://lists.<tld>/mailman3/archives/ url to.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Thank you for your hints. I got it working now, with base_url: http://127.0.0.1:8000/archives/ The problem was home made: I had mixed up the ports 8000 and 8001.
participants (2)
-
Eggert Ehmke -
Mark Sapiro