From abhijith@teknik.io Thu Jan 3 03:58:06 2019 From: Abhijith PA To: mailman-users@mailman3.org Subject: [MM3-users] Re: Getting Archives to work - new setup on Ubuntu 18.04 (with mailman3-full pkg) Date: Thu, 03 Jan 2019 09:28:00 +0530 Message-ID: <594273fd-c0d5-b805-04a4-274d254cebf0@teknik.io> In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============7772708156887694234==" --===============7772708156887694234== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Hi On Thursday 03 January 2019 06:39 AM, kelly.close(a)lrewater.com wrote: > Yes - lists are known to Hyperkitty but no, no Archived-At header > in received posts. > > But, Bingo! > > I hadn't looked at the log file immediately after trying to post a > message so I missed this. I don't know the solution yet but ... > what is this telling me? Something doesn't have the permissions it > needs somewhere... > > Jan 02 18:01:15 2019 (616) 127.0.0.1 - - "GET > /3.0/lists/mailman3_test.udfcd-lists.org/member/udfcd.alert(a)gmail.com > HTTP/1.1" 200 484 Jan 02 18:01:18 2019 (609) ACCEPT: > <20190103010115.530.63813(a)udmailman> Jan 02 18:01:18 2019 (615) > HyperKitty failure on > https://udfcd-lists.org/mailman3/hyperkitty/api/mailman/urls: > Auth requiredAuthorization > Required (401) ... (that line repeates 4 times) > Jan 02 18:01:20 2019 (606) Exception in the HyperKitty archiver: > Auth required

Authorization > Required

Jan 02 18:01:20 2019 (606) Traceback > (most recent call last): File > "/usr/lib/python3/dist-packages/mailman_hyperkitty/__init__.py", > line 154, in _archive_message url = self._send_message(mlist, msg) > File > "/usr/lib/python3/dist-packages/mailman_hyperkitty/__init__.py", > line 210, in _send_message raise ValueError(result.text) > ValueError: Auth required >

Authorization Required

What is your base_url in mailman-hyperkitty.cfg ? --a --===============7772708156887694234==-- From kelly.close@lrewater.com Thu Jan 3 16:56:59 2019 From: kelly.close@lrewater.com To: mailman-users@mailman3.org Subject: [MM3-users] Re: Getting Archives to work - new setup on Ubuntu 18.04 (with mailman3-full pkg) Date: Thu, 03 Jan 2019 16:56:56 +0000 Message-ID: <154653461667.486.16971123542030747795@mailman.iad1.psf.io> In-Reply-To: <594273fd-c0d5-b805-04a4-274d254cebf0@teknik.io> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============3237248403776872580==" --===============3237248403776872580== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit I have it set to: https://udfcd-lists.org/mailman3/hyperkitty/ --===============3237248403776872580==-- From kelly.close@lrewater.com Thu Jan 3 17:32:11 2019 From: kelly.close@lrewater.com To: mailman-users@mailman3.org Subject: [MM3-users] Re: Getting Archives to work - new setup on Ubuntu 18.04 (with mailman3-full pkg) Date: Thu, 03 Jan 2019 17:32:08 +0000 Message-ID: <154653672897.484.3042300229394497727@mailman.iad1.psf.io> In-Reply-To: <594273fd-c0d5-b805-04a4-274d254cebf0@teknik.io> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1965796438382158218==" --===============1965796438382158218== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Based on your question I experimented a little. I changed the base_url to ex= clude the hyperkitty/ at the end, so just https://udfcd-lists.org/mailman3/ With this I get a similar *looking* set of error lines in the log but now ins= tead of an authorization error it's a "was not found" error, so I think the b= ase_url is correct. This looks like a permissions problem related to the API - maybe I don't have= a key set properly somewhere...? --===============1965796438382158218==--