After sending mail to a list, it is not reflecting back in Hyperkitty archive. Kindly help me in this regard.
On 10/28/25 03:22, nirmal--- via Mailman-users wrote:
After sending mail to a list, it is not reflecting back in Hyperkitty archive. Kindly help me in this regard.
Are there files in Mailman's var/archives/hyperkitty/spool/ direrctory?
What's in Mailman's var/logs/mailman.log?
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Yes, There are files in that Directory.
root@list1:/var/lib/mailman3/archives/hyperkitty/spool# ls 1761648373.8935+904b919ee2129941efb5359d7fbc08cc66e154c8.pck 1761648373.917401+f2d75be071a12b44949318373ebcb0b05cf8341e.pck root@list1:/var/lib/mailman3/archives/hyperkitty/spool#
The Mailmans var.logs/mailman.log contains root@list1:/var/log/mailman3# cat mailman.log Oct 29 00:00:03 2025 (678809) Master watcher caught SIGHUP. Re-opening log files. Oct 29 00:00:03 2025 (678814) archive runner caught SIGHUP. Reopening logs. Oct 29 00:00:03 2025 (678826) task runner caught SIGHUP. Reopening logs. Oct 29 00:00:03 2025 (678815) bounces runner caught SIGHUP. Reopening logs. Oct 29 00:00:03 2025 (678816) command runner caught SIGHUP. Reopening logs. Oct 29 00:00:03 2025 (678818) lmtp runner caught SIGHUP. Reopening logs. Oct 29 00:00:03 2025 (678827) virgin runner caught SIGHUP. Reopening logs. Oct 29 00:00:03 2025 (678820) out runner caught SIGHUP. Reopening logs. Oct 29 00:00:03 2025 (678821) pipeline runner caught SIGHUP. Reopening logs. Oct 29 00:00:03 2025 (678817) in runner caught SIGHUP. Reopening logs. Oct 29 00:00:03 2025 (678828) digest runner caught SIGHUP. Reopening logs. Oct 29 00:00:03 2025 (678819) nntp runner caught SIGHUP. Reopening logs. Oct 29 00:00:03 2025 (678823) retry runner caught SIGHUP. Reopening logs. [2025-10-29 00:00:03 +0530] [683726] [INFO] Booting worker with pid: 683726 [2025-10-29 00:00:03 +0530] [678822] [WARNING] Worker with pid 678843 was terminated due to signal 15 [2025-10-29 00:00:03 +0530] [683727] [INFO] Booting worker with pid: 683727 [2025-10-29 00:00:03 +0530] [678822] [WARNING] Worker with pid 678844 was terminated due to signal 15 Oct 29 00:14:05 2025 (678826) Task runner evicted 0 expired pendings Oct 29 00:14:05 2025 (678826) Task runner deleted 0 orphaned workflows Oct 29 00:14:05 2025 (678826) Task runner deleted 0 orphaned requests Oct 29 00:14:05 2025 (678826) Task runner deleted 0 orphaned messages Oct 29 00:14:05 2025 (678826) Task runner evicted expired cache entries [29/Oct/2025:01:00:02 +0530] "GET /3.1/lists?count=10&page=1 HTTP/1.1" 200 473 "-" "GNU Mailman REST client v3.3.5" Oct 29 01:14:05 2025 (678826) Task runner evicted 0 expired pendings Oct 29 01:14:05 2025 (678826) Task runner deleted 0 orphaned workflows Oct 29 01:14:05 2025 (678826) Task runner deleted 0 orphaned requests Oct 29 01:14:05 2025 (678826) Task runner deleted 0 orphaned messages Oct 29 01:14:05 2025 (678826) Task runner evicted expired cache entries [29/Oct/2025:02:00:01 +0530] "GET /3.1/lists?count=10&page=1 HTTP/1.1" 200 473 "-" "GNU Mailman REST client v3.3.5" Oct 29 02:14:05 2025 (678826) Task runner evicted 0 expired pendings Oct 29 02:14:05 2025 (678826) Task runner deleted 0 orphaned workflows Oct 29 02:14:05 2025 (678826) Task runner deleted 0 orphaned requests Oct 29 02:14:05 2025 (678826) Task runner deleted 0 orphaned messages Oct 29 02:14:05 2025 (678826) Task runner evicted expired cache entries [29/Oct/2025:03:00:02 +0530] "GET /3.1/lists?count=10&page=1 HTTP/1.1" 200 473 "-" "GNU Mailman REST client v3.3.5" Oct 29 03:14:05 2025 (678826) Task runner evicted 0 expired pendings Oct 29 03:14:05 2025 (678826) Task runner deleted 0 orphaned workflows Oct 29 03:14:05 2025 (678826) Task runner deleted 0 orphaned requests Oct 29 03:14:05 2025 (678826) Task runner deleted 0 orphaned messages Oct 29 03:14:05 2025 (678826) Task runner evicted expired cache entries [29/Oct/2025:04:00:02 +0530] "GET /3.1/lists?count=10&page=1 HTTP/1.1" 200 473 "-" "GNU Mailman REST client v3.3.5" Oct 29 04:14:05 2025 (678826) Task runner evicted 0 expired pendings Oct 29 04:14:05 2025 (678826) Task runner deleted 0 orphaned workflows Oct 29 04:14:05 2025 (678826) Task runner deleted 0 orphaned requests Oct 29 04:14:05 2025 (678826) Task runner deleted 0 orphaned messages Oct 29 04:14:05 2025 (678826) Task runner evicted expired cache entries [29/Oct/2025:05:00:01 +0530] "GET /3.1/lists?count=10&page=1 HTTP/1.1" 200 473 "-" "GNU Mailman REST client v3.3.5" Oct 29 05:14:05 2025 (678826) Task runner evicted 0 expired pendings Oct 29 05:14:05 2025 (678826) Task runner deleted 0 orphaned workflows Oct 29 05:14:05 2025 (678826) Task runner deleted 0 orphaned requests Oct 29 05:14:05 2025 (678826) Task runner deleted 0 orphaned messages Oct 29 05:14:05 2025 (678826) Task runner evicted expired cache entries [29/Oct/2025:06:00:02 +0530] "GET /3.1/lists?count=10&page=1 HTTP/1.1" 200 473 "-" "GNU Mailman REST client v3.3.5" Oct 29 06:14:05 2025 (678826) Task runner evicted 0 expired pendings Oct 29 06:14:05 2025 (678826) Task runner deleted 0 orphaned workflows Oct 29 06:14:05 2025 (678826) Task runner deleted 0 orphaned requests Oct 29 06:14:05 2025 (678826) Task runner deleted 0 orphaned messages Oct 29 06:14:05 2025 (678826) Task runner evicted expired cache entries [29/Oct/2025:07:00:01 +0530] "GET /3.1/lists?count=10&page=1 HTTP/1.1" 200 473 "-" "GNU Mailman REST client v3.3.5" Oct 29 07:14:05 2025 (678826) Task runner evicted 0 expired pendings Oct 29 07:14:05 2025 (678826) Task runner deleted 0 orphaned workflows Oct 29 07:14:05 2025 (678826) Task runner deleted 0 orphaned requests Oct 29 07:14:05 2025 (678826) Task runner deleted 0 orphaned messages Oct 29 07:14:05 2025 (678826) Task runner evicted expired cache entries [29/Oct/2025:08:00:02 +0530] "GET /3.1/lists?count=10&page=1 HTTP/1.1" 200 473 "-" "GNU Mailman REST client v3.3.5" Oct 29 08:14:05 2025 (678826) Task runner evicted 0 expired pendings Oct 29 08:14:05 2025 (678826) Task runner deleted 0 orphaned workflows Oct 29 08:14:05 2025 (678826) Task runner deleted 0 orphaned requests Oct 29 08:14:05 2025 (678826) Task runner deleted 0 orphaned messages Oct 29 08:14:05 2025 (678826) Task runner evicted expired cache entries [29/Oct/2025:09:00:02 +0530] "GET /3.1/lists?count=10&page=1 HTTP/1.1" 200 473 "-" "GNU Mailman REST client v3.3.5" Oct 29 09:14:05 2025 (678826) Task runner evicted 0 expired pendings Oct 29 09:14:05 2025 (678826) Task runner deleted 0 orphaned workflows Oct 29 09:14:05 2025 (678826) Task runner deleted 0 orphaned requests Oct 29 09:14:05 2025 (678826) Task runner deleted 0 orphaned messages Oct 29 09:14:05 2025 (678826) Task runner evicted expired cache entries
-----Original Message----- From: Mark <mark@msapiro.net> To: mailman-users <mailman-users@mailman3.org> Date: Tuesday, 28 October 2025 9:16 PM IST Subject: [MM3-users] Re: Archive not working - Reg.
On 10/28/25 03:22, nirmal--- via Mailman-users wrote:
After sending mail to a list, it is not reflecting back in Hyperkitty archive. Kindly help me in this regard.
Are there files in Mailman's var/archives/hyperkitty/spool/ direrctory?
What's in Mailman's var/logs/mailman.log?
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
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/ Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message/...
This message sent to nirmal@iitm.ac.in
Nirmal J via Mailman-users writes:
Yes, There are files in that Directory.
root@list1:/var/lib/mailman3/archives/hyperkitty/spool# ls 1761648373.8935+904b919ee2129941efb5359d7fbc08cc66e154c8.pck 1761648373.917401+f2d75be071a12b44949318373ebcb0b05cf8341e.pck root@list1:/var/lib/mailman3/archives/hyperkitty/spool#
This indicates that HyperKitty is not picking up the queued files. Is mailman-hyperkitty installed? Is it configured correctly and enabled in mailman.cfg?
The Mailmans var.logs/mailman.log contains root@list1:/var/log/mailman3# cat mailman.log
This is today's log and shows no evidence of mail being received. Please look for older rotated logs (they typically look like mailman.log.1 and mailman.log.2.gz).
Specifically, in the log there should be notification that the mail was accepted like: Jan 02 20:46:31 2025 (167424) ACCEPT: <26486.63741.632755.297346@ip-192-168-11-5.eu-west-1.compute.internal>
What we are now looking for in that file is evidence of attempts to send to HyperKitty which look like these: Jan 02 20:46:32 2025 (167421) HyperKitty archiver processing queued filebase: 1735850598.983 318+a12b7afd6b238d1547d6ebda2f6b8e58ddd56046 Jan 02 20:46:32 2025 (167421) hyperkitty archiver: sending message <26486.64097.918721.71938@ip-192-168-11-5.eu-west-1.compute.internal>
and information about any failures.
Steve
-- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan
While I am opening mailman.log.1 It is displaying this.
Oct 28 15:46:08 2025 (678437) Task runner deleted 0 orphaned messages Oct 28 15:46:08 2025 (678437) Task runner evicted expired cache entries Oct 28 15:46:08 2025 (678438) virgin runner started. Oct 28 15:46:08 2025 (678433) out runner started. Oct 28 15:46:08 2025 (678427) archive runner started. Oct 28 15:46:09 2025 (678439) digest runner started. Oct 28 15:46:09 2025 (678428) bounces runner started. [28/Oct/2025:15:46:24 +0530] "GET /3.1/users/nirmal@iitm.ac.in HTTP/1.1" 200 395 "-" "GNU Mailman REST client v3.3.5" [28/Oct/2025:15:46:25 +0530] "GET /3.1/users/16963207e82d4315b2bfda3c5dfaad65 HTTP/1.1" 200 395 "-" "GNU Mailman REST client v3.3.5" [28/Oct/2025:15:46:25 +0530] "GET /3.1/users/16963207e82d4315b2bfda3c5dfaad65/addresses HTTP/1.1" 200 473 "-" "GNU Mailman REST client v3.3.5" [28/Oct/2025:15:46:25 +0530] "POST /3.1/members/find HTTP/1.1" 200 1379 "-" "GNU Mailman REST client v3.3.5" [28/Oct/2025:15:46:25 +0530] "GET /3.1/addresses/nirmal@iitm.ac.in HTTP/1.1" 200 368 "-" "GNU Mailman REST client v3.3.5" [28/Oct/2025:15:46:33 +0530] "GET /3.1/addresses/nirmal@iitm.ac.in HTTP/1.1" 200 368 "-" "GNU Mailman REST client v3.3.5" [28/Oct/2025:15:46:33 +0530] "GET /3.1/addresses/nirmal@iitm.ac.in HTTP/1.1" 200 368 "-" "GNU Mailman REST client v3.3.5" [28/Oct/2025:15:46:33 +0530] "GET /3.1/lists/staff.list1.iitm.ac.in HTTP/1.1" 200 368 "-" "GNU Mailman REST client v3.3.5" [28/Oct/2025:15:46:33 +0530] "GET /3.1/lists/staff@list1.iitm.ac.in/config HTTP/1.1" 200 3044 "-" "GNU Mailman REST client v3.3.5" [28/Oct/2025:15:46:33 +0530] "GET /3.1/lists/staff.list1.iitm.ac.in/member/nirmal%40iitm.ac.in HTTP/1.1" 200 648 "-" "GNU Mailman REST client v3.3.5" Oct 28 15:46:33 2025 (678430) ACCEPT: <176164659325.678449.14176354478536014912@list1.iitm.ac.in> Oct 28 15:46:34 2025 (678434) Exception in "hyperkitty" archiver Traceback (most recent call last): File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line 705, in urlopen httplib_response = self._make_request( ^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line 388, in _make_request self._validate_conn(conn) File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line 1050, in _validate_conn conn.connect() File "/usr/lib/python3/dist-packages/urllib3/connection.py", line 414, in connect self.sock = ssl_wrap_socket( ^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/urllib3/util/ssl_.py", line 449, in ssl_wrap_socket ssl_sock = _ssl_wrap_socket_impl( ^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/urllib3/util/ssl_.py", line 493, in _ssl_wrap_socket_impl return ssl_context.wrap_socket(sock, server_hostname=server_hostname) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.11/ssl.py", line 517, in wrap_socket return self.sslsocket_class._create( ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.11/ssl.py", line 1108, in _create self.do_handshake() File "/usr/lib/python3.11/ssl.py", line 1379, in do_handshake self._sslobj.do_handshake() ssl.SSLCertVerificationError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:992)
During handling of the above exception, another exception occurred:
Traceback (most recent call last): File "/usr/lib/python3/dist-packages/requests/adapters.py", line 489, in send resp = conn.urlopen( ^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line 789, in urlopen retries = retries.increment( ^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/urllib3/util/retry.py", line 594, in increment raise MaxRetryError(_pool, url, error or ResponseError(cause)) urllib3.exceptions.MaxRetryError: HTTPSConnectionPool(host='list1.iitm.ac.in', port=443): Max retries exceeded with url: /hyperkitty/api/mailman/urls?mlist=staff%40list1.iitm.ac.in (Caused by SSLError(SSLCertVerificationError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:992)')))
During handling of the above exception, another exception occurred:
Traceback (most recent call last): File "/usr/lib/python3/dist-packages/mailman/handlers/rfc_2369.py", line 87, in process archiver_url = archiver.system_archiver.list_url(mlist) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.11/dist-packages/mailman_hyperkitty-1.2.0-py3.11.egg/mailman_hyperkitty/__init__.py", line 108, in list_url return self._get_url(mlist, {"mlist": mlist.fqdn_listname}) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.11/dist-packages/mailman_hyperkitty-1.2.0-py3.11.egg/mailman_hyperkitty/__init__.py", line 89, in _get_url result = requests.get(url, params=params, headers=self.headers) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/requests/api.py", line 73, in get return request("get", url, params=params, **kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/requests/api.py", line 59, in request return session.request(method=method, url=url, **kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/requests/sessions.py", line 587, in request resp = self.send(prep, **send_kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/requests/sessions.py", line 701, in send r = adapter.send(request, **kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/requests/adapters.py", line 563, in send raise SSLError(e, request=request) requests.exceptions.SSLError: HTTPSConnectionPool(host='list1.iitm.ac.in', port=443): Max retries exceeded with url: /hyperkitty/api/mailman/urls?mlist=staff%40list1.iitm.ac.in (Caused by SSLError(SSLCertVerificationError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:992)'))) Oct 28 15:46:34 2025 (678434) Exception in "hyperkitty" archiver Traceback (most recent call last): File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line 705, in urlopen httplib_response = self._make_request( ^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line 388, in _make_request self._validate_conn(conn) File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line 1050, in _validate_conn conn.connect() File "/usr/lib/python3/dist-packages/urllib3/connection.py", line 414, in connect self.sock = ssl_wrap_socket( ^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/urllib3/util/ssl_.py", line 449, in ssl_wrap_socket ssl_sock = _ssl_wrap_socket_impl( ^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/urllib3/util/ssl_.py", line 493, in _ssl_wrap_socket_impl return ssl_context.wrap_socket(sock, server_hostname=server_hostname) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.11/ssl.py", line 517, in wrap_socket return self.sslsocket_class._create( ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.11/ssl.py", line 1108, in _create self.do_handshake() File "/usr/lib/python3.11/ssl.py", line 1379, in do_handshake self._sslobj.do_handshake() ssl.SSLCertVerificationError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:992)
-----Original Message----- From: Stephen <steve@turnbull.jp> To: Nirmal <nirmal@iitm.ac.in> Cc: mailman-users <mailman-users@mailman3.org> Date: Wednesday, 29 October 2025 12:23 PM IST Subject: [MM3-users] Re: Archive not working - Reg.
Nirmal J via Mailman-users writes:
Yes, There are files in that Directory.
root@list1:/var/lib/mailman3/archives/hyperkitty/spool# ls 1761648373.8935+904b919ee2129941efb5359d7fbc08cc66e154c8.pck 1761648373.917401+f2d75be071a12b44949318373ebcb0b05cf8341e.pck root@list1:/var/lib/mailman3/archives/hyperkitty/spool#
This indicates that HyperKitty is not picking up the queued files. Is mailman-hyperkitty installed? Is it configured correctly and enabled in mailman.cfg?
The Mailmans var.logs/mailman.log contains root@list1:/var/log/mailman3# cat mailman.log
This is today's log and shows no evidence of mail being received. Please look for older rotated logs (they typically look like mailman.log.1 and mailman.log.2.gz).
Specifically, in the log there should be notification that the mail was accepted like: Jan 02 20:46:31 2025 (167424) ACCEPT: <26486.63741.632755.297346@ip-192-168-11-5.eu-west-1.compute.internal>
What we are now looking for in that file is evidence of attempts to send to HyperKitty which look like these: Jan 02 20:46:32 2025 (167421) HyperKitty archiver processing queued filebase: 1735850598.983 318+a12b7afd6b238d1547d6ebda2f6b8e58ddd56046 Jan 02 20:46:32 2025 (167421) hyperkitty archiver: sending message <26486.64097.918721.71938@ip-192-168-11-5.eu-west-1.compute.internal>
and information about any failures.
Steve
-- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan
Nirmal J via Mailman-users writes:
While I am opening mailman.log.1 It is displaying this.
Everything up to this ACCEPT is irrelevant:
Oct 28 15:46:33 2025 (678430) ACCEPT: <176164659325.678449.14176354478536014912@list1.iitm.ac.in>
Looks like the Mailman configuration is correct, at least up to the point of contacting the HyperKitty archiving code:
Oct 28 15:46:34 2025 (678434) Exception in "hyperkitty" archiver
But your TLS is misconfigured (probably not configured at all?):
ssl.SSLCertVerificationError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:992)
(Haven't we been here before?)
The most likely problem is that you did not configure the base_url in mailman-hyperkitty.cfg. If your SSL configuration is correct, then changing that line to something like
base_url: https://list1.iitm.ac.in/archives/
should do the trick (be careful, pretty sure it will be similar but the host part must match the SSL certificate used by the host).
In the most common installation, Mailman and HyperKitty are on the same host. If so, there's no point in using SSL. At least I cannot think of a scenario where an adversary can tap a local connection but doesn't have a dozen other ways to steal the same information. So if that is the case, an alternative to fixing the SSL configuration is to have a virtual host listening on port 80 that doesn't accept any requests except those reverse proxied to HyperKitty. Or even just going directly to http://localhost:8000/archive should work. (This has the possible disadvantage that accesses to HyperKitty from Mailman won't be logged by your webserver, but they will still normally be logged by HyperKitty itself I think.)
-- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan
Now the following error occurs:-
root@list1:/var/log/mailman3# curl -v -H "X-Api-Key: XXXXXXXX"
https://list1.iitm.ac.in/hyperkitty/api/mailman/urls
- Trying 10.24.5.52:443...
- Connected to list1.iitm.ac.in (10.24.5.52) port 443 (#0)
- ALPN: offers h2,http/1.1
- TLSv1.3 (OUT), TLS handshake, Client hello (1):
- CAfile: /etc/ssl/certs/ca-certificates.crt
- CApath: /etc/ssl/certs
- TLSv1.3 (IN), TLS handshake, Server hello (2):
- TLSv1.2 (IN), TLS handshake, Certificate (11):
- TLSv1.2 (IN), TLS handshake, Server key exchange (12):
- TLSv1.2 (IN), TLS handshake, Server finished (14):
- TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
- TLSv1.2 (OUT), TLS change cipher, Change cipher spec (1):
- TLSv1.2 (OUT), TLS handshake, Finished (20):
- TLSv1.2 (IN), TLS handshake, Finished (20):
- SSL connection using TLSv1.2 / ECDHE-RSA-AES256-GCM-SHA384
- ALPN: server accepted h2
- Server certificate:
- subject: C=IN; ST=Tamil Nadu; O=Indian Institute of Technology Madras; CN=*.iitm.ac.in
- start date: Dec 6 00:00:00 2024 GMT
- expire date: Jan 6 23:59:59 2026 GMT
- subjectAltName: host "list1.iitm.ac.in" matched cert's "*.iitm.ac.in"
- issuer: C=GB; ST=Greater Manchester; L=Salford; O=Sectigo Limited; CN=Sectigo RSA Organization Validation Secure Server CA
- SSL certificate verify ok.
- using HTTP/2
- h2h3 [:method: GET]
- h2h3 [:path: /hyperkitty/api/mailman/urls]
- h2h3 [:scheme: https]
- h2h3 [:authority: list1.iitm.ac.in]
- h2h3 [user-agent: curl/7.88.1]
- h2h3 [accept: */*]
- h2h3 [x-api-key: xxxxxxxxxx]
- Using Stream ID: 1 (easy handle 0x559f80a4f7a0)
GET /hyperkitty/api/mailman/urls HTTP/2 Host: list1.iitm.ac.in user-agent: curl/7.88.1 accept: */* x-api-key: XXXXXXXXX
< HTTP/2 401 < server: nginx < date: Wed, 29 Oct 2025 10:06:58 GMT < content-type: text/html < content-length: 226 < strict-transport-security: max-age=31536000; includeSubDomains; preload < x-content-type-options: nosniff < referrer-policy: same-origin < x-frame-options: DENY < vary: Accept-Language, Cookie < content-language: en < strict-transport-security: max-age=31536000; includeSubDomains < <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.
- Connection #0 to host list1.iitm.ac.in left intact. Kindly help me to resolve
-----Original Message----- From: Stephen <steve@turnbull.jp> To: Nirmal <nirmal@iitm.ac.in> Cc: Stephen <steve@turnbull.jp>; mailman-users <mailman-users@mailman3.org> Date: Wednesday, 29 October 2025 1:54 PM IST Subject: [MM3-users] Re: Archive not working - Reg.
Nirmal J via Mailman-users writes:
While I am opening mailman.log.1 It is displaying this.
Everything up to this ACCEPT is irrelevant:
Oct 28 15:46:33 2025 (678430) ACCEPT: <176164659325.678449.14176354478536014912@list1.iitm.ac.in>
Looks like the Mailman configuration is correct, at least up to the point of contacting the HyperKitty archiving code:
Oct 28 15:46:34 2025 (678434) Exception in "hyperkitty" archiver
But your TLS is misconfigured (probably not configured at all?):
ssl.SSLCertVerificationError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:992)
(Haven't we been here before?)
The most likely problem is that you did not configure the base_url in mailman-hyperkitty.cfg. If your SSL configuration is correct, then changing that line to something like
base_url: https://list1.iitm.ac.in/archives/
should do the trick (be careful, pretty sure it will be similar but the host part must match the SSL certificate used by the host).
In the most common installation, Mailman and HyperKitty are on the same host. If so, there's no point in using SSL. At least I cannot think of a scenario where an adversary can tap a local connection but doesn't have a dozen other ways to steal the same information. So if that is the case, an alternative to fixing the SSL configuration is to have a virtual host listening on port 80 that doesn't accept any requests except those reverse proxied to HyperKitty. Or even just going directly to http://localhost:8000/archive should work. (This has the possible disadvantage that accesses to HyperKitty from Mailman won't be logged by your webserver, but they will still normally be logged by HyperKitty itself I think.)
-- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan
Nirmal J via Mailman-users writes:
<h1>Authorization Required</h1><p>Please check whether the MAILMAN_ARCHIVER_KEY is provided by you and it is correct.
Find MAILMAN_ARCHIVER_KEY in settings.py and mailman-hyperkitty.cfg, and make sure they are the same and have correct syntax (settings.py is a Python source file and the value must be surrounded by matching quotation marks, while mailman-hyperkitty.cfg is a .ini-like file and values must not have quotation marks).
Please do more work at your end. I'm tired of doing your work for you, with you functioning as a very slow remote terminal. We've got good documentation as software documentation goes. Read it. In this message, you typed "help me" right under the key lines quoted above. If you won't read the log and try to find something you can understand, why should we do it for you? At the very least, when the error message says "Please check this variable", you should be able to do "grep this_variable /etc/mailman3/*" to find which files contain settings for it.
-- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan
participants (4)
-
Mark Sapiro -
Nirmal J -
nirmal＠iitm.ac.in
-
Stephen J. Turnbull