On 7/8/21 2:01 PM, Sarah H wrote:
here are the current configs and the files in spool.
in var/archives/hyperkitty/spool/
-rw-rw---- 1 mailman mailman 5.9K Jul 8 13:55 1625777713.5186543+0b1e6ae782342e699116994a4cc5968e8e01701c.pck -rw-rw---- 1 mailman mailman 5.8K Jul 8 13:55 1625777713.642453+2e79e4d69d3f91f72646af26822566116a98f92e.pck
There should be errors in Mailman's mailman.log for these. You can see
the actual message in the .pck by pointing mailman qfile at it.
mailman.cfg:
...
[archiver.hyperkitty] class: mailman_hyperkitty.Archiver enable: yes configuration: /etc/mailman3/mailman-hyperkitty.cfg
OK
mailman-hyperkitty.cfg
# This is the mailman extension configuration file to enable HyperKitty as an # archiver. Remember to add the following lines in the mailman.cfg file: # # [archiver.hyperkitty] # class: mailman_hyperkitty.Archiver # enable: yes # configuration: /path/to/here/mailman-hyperkitty.cfg #
[general]
# This is your HyperKitty installation, preferably on the localhost. This # address will be used by Mailman to forward incoming emails to HyperKitty # for archiving. It does not need to be publicly available, in fact it's # better if it is not. # However, if your Mailman installation is accessed via HTTPS, the URL needs # to match your SSL certificate (e.g. https://lists.example.com/hyperkitty). base_url: https://lists.siteurl.org/archives/
I assume that you have the real URL to hyperkitty here. I'm not sure, but https might be an issue.
# Shared API key, must be the identical to the value in HyperKitty's # settings. api_key: thisisnotreallymykey
settings.py
...
MAILMAN_ARCHIVER_KEY = 'thisisnotreallymykey'
OK
It looks OK. You should now see log messages regarding the messages in var/archives/hyperkitty/spool/. They should help.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan