hyperkitty not archiving new mail
Hello all,
Mailman 3.3.10 on Debian 13.
I recently upgraded from a well-running installation of Mailman2. Importing the existing mailing lists went well but I'm having problems with hyperkitty. First it was complaining that I didn't have a valid SSL certificate for localhost. I rectified that but in the mean time I ended up with some .pck files in /var/lib/mailman3/archives/hyperkitty/spool . Inspecting these with mailman-wrapper qfile reveals that they are messages which have been sent since the import. How do I reindex just those messages? I tried update_index and rebuild_index but apart from taking forever, they don't seem to help.
On 8/6/26 11:51, Jaldhar H. Vyas via Mailman-users wrote:
Hello all,
Mailman 3.3.10 on Debian 13.
I recently upgraded from a well-running installation of Mailman2. Importing the existing mailing lists went well but I'm having problems with hyperkitty. First it was complaining that I didn't have a valid SSL certificate for localhost. I rectified that but in the mean time I ended up with some .pck files in /var/lib/mailman3/archives/hyperkitty/spool . Inspecting these with mailman-wrapper qfile reveals that they are messages which have been sent since the import. How do I reindex just those messages? I tried update_index and rebuild_index but apart from taking forever, they don't seem to help.
They will be retried the next time a post is sent to HyperKitty to be archived. Assuming you fixed the underlying issue that caused them to fail, they will be archived at that time. If archiving continues to fail, there should be error messages logged in mailman.log with more info.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
I thought I had it fixed but apparently not. The problem now is that the SSL certificate, though valid, is self-signed which it (or the underlying Python library) doesn't like. Is their some setting I can adjust to bypass that check?
For the outward-facing web services I use certificates generated and signed by letsencrypt but it won't allow me to generate one for localhost.
On 8/7/26 13:14, Jaldhar H. Vyas via Mailman-users wrote:
I thought I had it fixed but apparently not. The problem now is that the SSL certificate, though valid, is self-signed which it (or the underlying Python library) doesn't like. Is their some setting I can adjust to bypass that check?
For the outward-facing web services I use certificates generated and signed by letsencrypt but it won't allow me to generate one for localhost.
I'm guessing you may have something like
[general] base_url: https://localhost/archives/
in /etc/mailman3/mailman-hyperkitty.cfg (or wherever it is)
You have a few choices for changing that. At least one of the following will work
base_url: http://localhost:8000/archives/
base_url: http://localhost/archives/ (this will only work if the webserver doesn't redirect http to https)
base_url: https://public.facing.domain/archives/
If yours has hyperkitty instead of archives, you can keep that.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Sorry just getting back to this. Your first suggestion seems to have done the trick but I have another problem which I will write about in a separate thread.
participants (2)
-
Jaldhar H. Vyas -
Mark Sapiro