Hi Mark,
Thanks. But that is not the problem. It's hyperkitty background processes that show the error in the logs. I was probably not clear in my statement of the problem. I was testing it by typing in URL's. Sorry!
I solved it by searching these archives. There was a post in January regarding the same issue, and the solution turned out to be replacing the given api keys with new ones, and all it all just works. Why that should be is a mystery to me, but now at least two people have found this. I would have thought a key is just a key.
Andrew
-----Original Message----- From: Mark Sapiro <mark@msapiro.net> Sent: Friday, 7 June 2019 1:22 AM To: mailman-users@mailman3.org Subject: [MM3-users] Re: Hyperkitty Authorization Required
You have to be logged in to post from HyperKitty. You can't post anonymously.