From bader@cchmc.org Thu Jun 9 19:09:17 2022 From: bob B To: mailman-users@mailman3.org Subject: [MM3-users] Turned on archiving and it is not working Date: Thu, 09 Jun 2022 19:09:13 +0000 Message-ID: <165480175393.3448.6174713145187201174@mailman.iad1.psf.io> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============5392855285126597009==" --===============5392855285126597009== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable I normally have archives not enabled on all my lists and I do not even have h= yperkitty 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 HyperKi= tty archiver: Auth required

Authorization Required

The archiv= er key is now File "/usr/lib/python3.8/site-packages/mailman_hyp= erkitty/__init__.py", line 154, in _archive_message

Authorization Required

The archiver key= is now

Authorization Required

The archiver ke= y is now I am running in docker: my HYPERKITTY_API_KEY is the same in my docker yaml file for mailman-core & m= ailman-web (I am using an external database) mailman info=20 GNU Mailman 3.3.5 (Tom Sawyer) Python 3.8.10 (default, May 6 2021, 06:30:44)=20 [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 no= w. Any thoughts on what to do next? --===============5392855285126597009==-- From mark@msapiro.net Thu Jun 9 19:33:34 2022 From: Mark Sapiro To: mailman-users@mailman3.org Subject: [MM3-users] Re: Turned on archiving and it is not working Date: Thu, 09 Jun 2022 12:33:22 -0700 Message-ID: <6207f0a5-ec1c-1a09-86d9-c0dabacf0146@msapiro.net> In-Reply-To: <165480175393.3448.6174713145187201174@mailman.iad1.psf.io> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============4886988507717724708==" --===============4886988507717724708== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable On 6/9/22 12:09, bob B via Mailman-users wrote: >=20 > Jun 09 18:49:10 2022 (28) Exception in the Hype= rKitty archiver: Auth required >

Authorization Required

The arc= hiver key is now > File "/usr/lib/python3.8/site-packages/mailman_= hyperkitty/__init__.py", line 154, in _archive_message >

Authorization Required

The archiver = key is now >

Authorization Required

The archiver= key is now The full message is

Authorization Required

The archiver key=20 is now required to be sent over the Authorization HTTP=20 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 >=3D 1.3.5 requires=20 mailman-hyperkitty >=3D 1.2.0 If your mailman-hyperkitty is < 1.2.0, you need to upgrade it. If it is=20 1.2.0, there is some issue with the http headers being dropped in the=20 request from mailman-hyperkitty to HyperKitty. See the last two posts in=20 the thread at=20 https://lists.mailman3.org/archives/list/mailman-users(a)mailman3.org/thread/= WSUEPQL6PX52Y7XVWYSSGJJXC7E3F6FG/ --=20 Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan --===============4886988507717724708==-- From bader@cchmc.org Thu Jun 9 19:47:19 2022 From: bob B To: mailman-users@mailman3.org Subject: [MM3-users] Re: Turned on archiving and it is not working Date: Thu, 09 Jun 2022 19:47:15 +0000 Message-ID: <165480403581.3448.3913375440985849708@mailman.iad1.psf.io> In-Reply-To: <6207f0a5-ec1c-1a09-86d9-c0dabacf0146@msapiro.net> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============5887992485103993222==" --===============5887992485103993222== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Mark, Thanks, So how do I check the version of mailman-hyperkitty? I thought tha= t was the HyperKitty version 1.3.5. that was displayed in the web interface, = but I assume that mailman-hyperkitty is something different? --===============5887992485103993222==-- From bader@cchmc.org Thu Jun 9 20:32:23 2022 From: bob B To: mailman-users@mailman3.org Subject: [MM3-users] Re: Turned on archiving and it is not working Date: Thu, 09 Jun 2022 20:32:20 +0000 Message-ID: <165480674010.3450.13111872951965705412@mailman.iad1.psf.io> In-Reply-To: <165480403581.3448.3913375440985849708@mailman.iad1.psf.io> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============4111763788885521399==" --===============4111763788885521399== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable 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 imag= e, I remember updating the docker images, but i thought I tested archiving af= ter that, but maybe not. maxking, Can you confirm? --===============4111763788885521399==-- From mark@msapiro.net Thu Jun 9 20:47:29 2022 From: Mark Sapiro To: mailman-users@mailman3.org Subject: [MM3-users] Re: Turned on archiving and it is not working Date: Thu, 09 Jun 2022 13:47:17 -0700 Message-ID: <61513499-d554-9ce8-4dcd-c2b4067b3b93@msapiro.net> In-Reply-To: <165480403581.3448.3913375440985849708@mailman.iad1.psf.io> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0717826486053607013==" --===============0717826486053607013== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable On 6/9/22 12:47, bob B via Mailman-users wrote: > Mark, >=20 > Thanks, So how do I check the version of mailman-hyperkitty? I thought t= hat 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",=20 line 154, in _archive_message` ``` The fact that it is line 154 says it is 1.1.0. You need to upgrade=20 mailman-hyperkitty. I don't know how to do that in your Docker=20 container. If you can run pip ``` pip install --upgrade mailman-hyperkitty ``` should do it. --=20 Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan --===============0717826486053607013==--