Hi Franklin,
when I installed mailman3 on Debian I had some issues. One was about MAILMAN_ARCHIVER_FROM. It turned out, that the request to Hyperkitty was sent from one of the real IPs of the machine (not from localhost). This depends on the interfaces and the routing of that machine. In my case the solution was something like:
MAILMAN_ARCHIVER_FROM = ('127.0.0.1', '::1', '1.2.3.4', '1.2.3.5') , where 1.2.3.4 and 1.2.3.5 are the IP addresses of the machine running mailman3 (I have not debugged if it is using .4 or .5 in reality I left both of them there). Give it a try with your IPs.
Tamás
- 8:52 keltezéssel, Franklin Weng írta:
Hi,
It looks like to have some clues now.
Mark Sapiro <mark@msapiro.net> 於 2019年10月30日 週三 13:07 寫道：
Yes, it is checked. Have you checked Mailman's logs - Mailman's var/logs/mailman.log in
On 10/29/19 8:21 PM, Franklin Weng wrote: particular?
I found some hyperkitty URL error:
The default settings of base_url in mailman-hyperkitty.cfg is defined as
base_url: http://localhost/mailman/hyperkitty/
In the mailman.log there are messages like:
Oct 30 13:53:43 2019 (14259) HyperKitty failure on http://localhost/mailman3/hyperkitty/api/mailman/archive: <!DOCTYPE HTML PUBLIC "-//IETF// DTD HTML 2.0//EN"> <html><head> <title>404 Not Found</title> </head><body> <h1>Not Found</h1> <p>The requested URL was not found on this server.</p>
I changed it to
base_url: https://localhost/mailman3/hyperkitty/
then the log became
File "/usr/lib/python3/dist-packages/requests /adapters.py", line 514, in send raise SSLError(e, request=request) requests.exceptions.SSLError: HTTPSConnectionPool(host='localhost', port=443): Max retries exceeded with url: /mailman3/hyperkitty/api/mailman/archive?key=xxx (Caused by SSLError(SSLCertVerification Error("hostname 'localhost' doesn't match ' lists.slat.org'")))
which makes sense because the SSL certificate applied from Letsencrypt is for lists.slat.org.
If I use
base_url: https://lists.slat.org/mailman3/hyperkitty/
The log became
Oct 30 15:25:50 2019 (6256) HyperKitty failure on https://lists.slat.org/mailman3/hyperkitty/api/mailman/urls: <html><title>Auth required</title><body>
<h1>Authorization Required</h1></body></html> (401)
In my mailman-web.py:
MAILMAN_ARCHIVER_KEY = 'my-key,same as in mailman-hyperkitty.cfg' MAILMAN_ARCHIVER_FROM = ('127.0.0.1', '::1')
Not sure what to change here.
Do messages received from the list have an Archived-At: header?
Yes, but it's empty
List-Id: 測試論壇 <slat-list.lists.slat.org> Archived-At: <> List-Archive: <> List-Help: <mailto:slat-list-request@lists.slat.org?subject=help> List-Post: <mailto:slat-list@lists.slat.org> List-Subscribe: <mailto:slat-list-join@lists.slat.org> List-Unsubscribe: <mailto:slat-list-leave@lists.slat.org>
What's in /etc/mailman3/mailman-hyperkitty.cfg? In particular does the [general] setting base_url define a URL that accesses hyperkitty
It seems to be the question…
and
does the [general] setting api_key match the MAILMAN_ARCHIVER_KEY setting in /etc/mailman3/mailman-web.py, but note that the MAILMAN_ARCHIVER_KEY setting is quotes because it is a Python string assignment and the api_key setting is not quoted
Yes, it's single quoted.
Thanks for all your help!
Franklin
Mailman-users mailing list -- mailman-users@mailman3.org To unsubscribe send an email to mailman-users-leave@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/