I normally have archives not enabled on all my lists and I do not even have hyperkitty enabled for them. but I need to turn on archiving for one list and it is not working. I made sure hyper kitty is enabled for the list, and I have private archives enabled. I even restarted my environment (more on that in a moment) and still the list works but nothing gets archived. my mail log shows
Jun 09 18:49:10 2022 (28) Exception in the HyperKitty archiver: <html><title>Auth required</title><body>
<h1>Authorization Required</h1><p>The archiver key is now
File "/usr/lib/python3.8/site-packages/mailman_hyperkitty/__init__.py", line 154, in _archive_message
<h1>Authorization Required</h1><p>The archiver key is now
<h1>Authorization Required</h1><p>The archiver key is nowI am running in docker: my HYPERKITTY_API_KEY is the same in my docker yaml file for mailman-core & mailman-web (I am using an external database)
mailman info GNU Mailman 3.3.5 (Tom Sawyer) Python 3.8.10 (default, May 6 2021, 06:30:44) [GCC 9.3.0]
Hyperkitty web interface is working and I can log in so it is up HyperKitty version 1.3.5.
This used to work when I initially installed, so not sure why it is broken now.
Any thoughts on what to do next?
On 6/9/22 12:09, bob B via Mailman-users wrote:
Jun 09 18:49:10 2022 (28) Exception in the HyperKitty archiver: <html><title>Auth required</title><body> <h1>Authorization Required</h1><p>The archiver key is now File "/usr/lib/python3.8/site-packages/mailman_hyperkitty/__init__.py", line 154, in _archive_message <h1>Authorization Required</h1><p>The archiver key is now <h1>Authorization Required</h1><p>The archiver key is now
The full message is
<h1>Authorization Required</h1><p>The 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.
HyperKitty version 1.3.5.
As indicated in the above message, HyperKitty >= 1.3.5 requires mailman-hyperkitty >= 1.2.0
If your mailman-hyperkitty is < 1.2.0, you need to upgrade it. If it is 1.2.0, there is some issue with the http headers being dropped in the request from mailman-hyperkitty to HyperKitty. See the last two posts in the thread at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/W...
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Mark,
Thanks, So how do I check the version of mailman-hyperkitty? I thought that was the HyperKitty version 1.3.5. that was displayed in the web interface, but I assume that mailman-hyperkitty is something different?
So I think i found it
in Mailman-core bash-5.0$ pip list Package Version
. . mailman-hyperkitty 1.1.0
So I believe this has been broken since I updated with the latest docker image, I remember updating the docker images, but i thought I tested archiving after that, but maybe not.
maxking,
Can you confirm?
On 6/9/22 12:47, bob B via Mailman-users wrote:
Mark,
Thanks, So how do I check the version of mailman-hyperkitty? I thought that was the HyperKitty version 1.3.5. that was displayed in the web interface, but I assume that mailman-hyperkitty is something different?
Yes. mailman-hyperkitty is a shim between Mailman core and HyperKitty.
Your mail message has `` File "/usr/lib/python3.8/site-packages/mailman_hyperkitty/__init__.py", line 154, in _archive_message`
The fact that it is line 154 says it is 1.1.0. You need to upgrade
mailman-hyperkitty. I don't know how to do that in your Docker
container. If you can run pip
pip install --upgrade mailman-hyperkitty
should do it.
--
Mark Sapiro <mark@msapiro.net> The highway is for gamblers,
San Francisco Bay Area, California better use your sense - B. Dylan
participants (2)
-
bob B -
Mark Sapiro