Dear all,
Sorry for coming back to a topic that seems to be done for 18 months now.
I'm staring at this issue for a few days now (on and off). But I still get these messages:
Jan 19 22:43:27 2022 (149439) HyperKitty failure on https://lists.[...]/hyperkitty/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). and consequently, nothing ends up in the archive.
I have checked (among others):
MAILMAN_ARCHIVER_FROM - doesn't make a difference. 127.0.0.1, external IP address, different orders, '*'.
(Asterisk makes a difference, see at the bottom)MAILMAN_ARCHIVER_KEY in mailman-web.py matches api_key in mailman-hyperkitty.cfg (except for the quotes). According to the editor's
color coding, the quotes are "right", too. I have removed special characters to circumvent diverging treatment in different environments
I guess it doesn't matter, but wget --user restadmin --password [.] http://localhost:8001/3.1/lists works, too.
ACCOUNT_DEFAULT_HTTP_PROTOCOL = "https" (probably also doesn't matter
I'm running a fresh package installation from Debian Bullseye with certificates from Certbot with nginx, so Certbot may have messed with my nginx config, but even that seems to be OK: Yes, Certbot has inserted http->https redirection, but I'd expect that a https base_url and ACCOUNT_DEFAULT_HTTP_PROTOCOL = "https" circumvents that.
Mailman info says
GNU Mailman 3.3.3 (Tom Sawyer)
Python 3.9.2 (default, Feb 28 2021, 17:03:44)
[GCC 10.2.1 20210110]
.
REST root url: http://localhost:8001/3.1/
Hyperkitty is 1.3.4, Postorious is 1.3.4, too.
To provide all possible information, I'm also adding the nginx log that seems to correspond to that request (no other requests at that time, give or take five minutes): Yes, everything yields 403 response codes.
[.] - - [19/Jan/2022:22:43:27 +0000] "GET /hyperkitty/api/mailman/urls?mlist=demo%40lists.pro-digi-par.de&key=[.] HTTP/1.1" 403 175 "-" "python-requests/2.25.1"
[.] - - [19/Jan/2022:22:43:27 +0000] "GET /hyperkitty/api/mailman/urls?mlist=demo%40lists.pro-digi-par.de&msgid=AM0PR0 4MB478573911C2A81B8898527E6C2599%40AM0PR04MB4785.eurprd04.prod.outlook.com&k ey=[.] HTTP/1.1
" 403 175 "-" "python-requests/2.25.1"
[.] - - [19/Jan/2022:22:43:28 +0000] "GET /hyperkitty/api/mailman/urls?mlist=demo%40lists.pro-digi-par.de&msgid=AM0PR0 4MB478573911C2A81B8898527E6C2599%40AM0PR04MB4785.eurprd04.prod.outlook.com&k ey=[.] HTTP/1.1
" 403 175 "-" "python-requests/2.25.1"
[.] - - [19/Jan/2022:22:43:28 +0000] "POST /hyperkitty/api/mailman/archive?key=[.] HTTP/1.1" 403 166 "-" "python-requests/2.25.1"
[.] - - [19/Jan/2022:22:43:28 +0000] "POST /hyperkitty/api/mailman/archive?key=[.] HTTP/1.1" 403 166 "-" "python-requests/2.25.1"
. repeated many times, there seems to be quite a few testmessages in the queue .
[.] - - [19/Jan/2022:22:46:50 +0000] "GET /hyperkitty/api/mailman/urls?mlist=demo%40lists.pro-digi-par.de&key=[.] HTTP/1.1" 403 175 "-" "python-requests/2.25.1"
[.] - - [19/Jan/2022:22:46:50 +0000] "GET /hyperkitty/api/mailman/urls?mlist=demo%40lists.pro-digi-par.de&msgid=AM0PR0 4MB4785430188B9C0E8DF248231C2599%40AM0PR04MB4785.eurprd04.prod.outlook.com&k ey=6xpENHLEHQ0kD53vXt5RpKzPDOsKbcN9 HTTP/1.1
" 403 175 "-" "python-requests/2.25.1"
[.] - - [19/Jan/2022:22:46:50 +0000] "POST /hyperkitty/api/mailman/archive?key=[.] HTTP/1.1" 403 166 "-" "python-requests/2.25.1"
. again repeated many times .
[.] - - [19/Jan/2022:22:46:51 +0000] "GET /hyperkitty/api/mailman/urls?mlist=demo%40lists.pro-digi-par.de&msgid=AM0PR0 4MB4785430188B9C0E8DF248231C2599%40AM0PR04MB4785.eurprd04.prod.outlook.com&k ey=[.] HTTP/1.1" 403 175 "-" "python-requests/2.25.1"
I'd appreciate a new idea where I could look for clues.
Thanks a lot,
Josef