On 12/9/2020 1:49 PM, Mark Sapiro wrote:
On 12/8/20 11:37 PM, Morris Jones wrote:
I created a mailman-hyperkitty.cfg file in /opt/mailman/var/etc/.
You need to set
configuration: /opt/mailman/var/etc/mailman-hyperkitty.cfg
did that ...
If it redirects to https, set it to https to avoid the redirect.
did that as well ...
base_url: https://mailman.whiteoaks.com/hyperkitty/
(Though the configuration comment on this suggests it should not be publicly accessible, I don't see any alternative endpoint that's private.)
I added both my public IP address and my domain name to MAILMAN_ARCHIVER_FROM.
So this part is all set, it would seem ...
[archive.hyperkitty]
class: mailman_hyperkitty.Archiver
enable: yes
configuration: /opt/mailman/var/etc/mailman-hyperkitty.cfg
[logging.archiver]
path: /opt/mailman/var/logs/archiver.log api_keyMy archiver log continues empty
The API keys match in settings_local.py MAILMAN_ARCHIVER_FROM and mailman-hyperkitty.cfg
Eric Broens suggested a curl to the endpoint to check for errors:
From that I get:
$ curl -i https://mailman.whiteoaks.com/hyperkitty/api/mailman/urls HTTP/1.1 401 Unauthorized Server: nginx Date: Thu, 10 Dec 2020 00:55:45 GMT Content-Type: text/html Content-Length: 226 Connection: keep-alive X-Content-Type-Options: nosniff X-Frame-Options: DENY Vary: Accept-Language, Cookie Content-Language: en
<html><title>Auth required</title><body> <h1>Authorization Required</h1><p>Please check whether the MAILMAN_ARCHIVER_KEY is provided by you and it is correct. </p></body></html>
Presumably I didn't provide the key in the header.
archiver.log remains empty, and mailman.log has no references to the archiver.
The hyperkitty UI is presenting fine, but no messages are archived.
Best regards, Mojo
Morris Jones, Monrovia, CA BridgeMojo <http://bridgemojo.com> Old Town Sidewalk Astronomers <http://otastro.org> Mojo's Blog <http://mojo.whiteoaks.com>