The issue is not related to message content. One possibility is that there is an incompatibility between mailman-hyperkitty >= 1.2.0 and HyperKitty <= 1.3.4. that could cause this. What are your versions? Understood, just wanted to mention that as I read it in another thread about the 401. Hyperkitty is 1.3.4 and mailman-hyperkitty is 1.2.0 What is your setting in mailman-hyperkitty.cfg for base_url:
Mark Sapiro wrote: base_url is set to https://www.fqdn.tld/mailman/hyperkitty
if you append api/ to that and do something like curl base_url/api/ it should return a page of documentation of the API. If that is the case, the issue is almost certainly communicating the api key between mailman-hyperkitty and HyperKitty I get some information back when appending /api/ to that URL mentioned above about REST API and some formats and endpoints. So, from your words it looks like there is some issue in the communication between mailman-hyperkitty and HyperKitty. Is there some place I could/should start looking or some log I should be examining (maybe some loglevel to be increased as well)?