On 10/22/21 8:51 AM, Marco Marinello wrote:
Hi everybody,
as per subject, I'm getting this error in the hyperkitty log when mailman daemon tries to archive a mail. I've setup the hyperkitty.cfg file with api_key = MAILMAN_ARCHIVER_KEY in settings_local.py but still nothing. I've seen here and in GitLab issues some errors concerning a wrong api key but here it says that it wasn't sent at all. All packages installed via pip install + latest .zip release, including mailman-hyperkitty. Currently running on apache with mod_wsgi_py3 without https.
The following combinations should work:
mailman-hyperkitty 1.2.0 with HyperKitty 1.3.5
mailman-hyperkitty <1.2.0 with HyperKitty <1.3.5
The following will not work:
mailman-hyperkitty 1.2.0 with HyperKitty <1.3.5
mailman-hyperkitty <1.2.0 with HyperKitty 1.3.5
Do you see a message like 'The MAILMAN_ARCHIVER_KEY is now required to be sent over the Authorization HTTP header, you need to upgrade the mailman-hyperkitty package to 1.2.0 or newer.'
In your Django log and/or your mailman.log? These will only be logged with HyperKitty 1.3.5 and mailman-hyperkitty < 1.2.0
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan