Hi, in mailman log I found:
Jun 20 17:36:49 2020 (1269) HyperKitty failure on http://localhost/mailman3/hyperkitty/api/mailman/urls: <html><title>Forbidden</title><body> <h1>Access is forbidden</h1></body></html> (403) Jun 20 17:36:49 2020 (1263) HyperKitty failure on http://localhost/mailman3/hyperkitty/api/mailman/archive: (405) Jun 20 17:36:49 2020 (1263) Exception in the HyperKitty archiver: Jun 20 17:36:49 2020 (1263) Traceback (most recent call last): File "/usr/lib/python3/dist-packages/mailman_hyperkitty/__init__.py", line 154, in _archive_message url = self._send_message(mlist, msg) File "/usr/lib/python3/dist-packages/mailman_hyperkitty/__init__.py", line 210, in _send_message raise ValueError(result.text) ValueError
And checking archive list I notice nothing has been added.
Is it a permission issue (where?) or something else?
Thanks in advance.
-- Gelpi ing. Andrea
It took the computing power of three C-64s to fly to the Moon. It takes a 486 to run Windows 95. Something is wrong here.
I ran into this same error over the weekend and posted this fix - hopefully it will help you! https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message/...
Be sure also that you've addressed the other possiblitites: matching api_key/ARCHIVER_KEY, the base URL and ARCHIVER_FROM, and allowed hosts. But for me all those things were fine, but I think because I used certbot to install SSL certificates after I had already set up the mailman3 server, and I accepted the certbot "redirect everything" option, localhost conversations with hyperkitty were getting blocked. Good luck.
Just a quick qualifier regarding this post - I tried to reference those environment variables from memory and missed. MAIL_FROM is what I meant by "archiver_from" - sorry for any confusion.
Il 22/06/20 21:08, kelly.close@lrewater.com ha scritto:
I ran into this same error over the weekend and posted this fix - hopefully it will help you! https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message/...
Be sure also that you've addressed the other possiblitites: matching api_key/ARCHIVER_KEY, the base URL and ARCHIVER_FROM, and allowed hosts. But for me all those things were fine, but I think because I used certbot to install SSL certificates after I had already set up the mailman3 server, and I accepted the certbot "redirect everything" option, localhost conversations with hyperkitty were getting blocked. Good luck.
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/
Thank You so much. Adding the virtual host solved the problem.
-- Gelpi ing. Andrea
It took the computing power of three C-64s to fly to the Moon. It takes a 486 to run Windows 95. Something is wrong here.
See my reply at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message/... for the preferred way to fix this.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
participants (3)
-
Gelpi Andrea -
kelly.close＠lrewater.com -
Mark Sapiro