On 6/24/20 8:30 AM, Kelly Close wrote:
I suspect then that my MAILMAN_ARCHIVER_FROM setting is deficient or... that ACCOUNT_DEFAULT_HTTP_PROTOCOL variable is a new one to me - I don't think I have that set anyplace. Perhaps that would have helped?
I don't think so. ACCOUNT_DEFAULT_HTTP_PROTOCOL is a Django allauth setting and I think only affects things like logging in to Django.
MAILMAN_ARCHIVER_FROM is definitely relevant.
I'm going to leave it be for now since the listener did the trick, but I will also copy these remarks into my Ubuntu 18.04 Mailman3 setup guide which just keeps getting better over time! Thanks.
The bottom line here is if the only thing that changed that allowed things to work was creating a virtual host in Apache for 127.0.0.1:80 to not redirect to https, then Mailman core must have been (must be) going to port 80 (http). You've probably already done this more than once, but I suggest giving the following command
mailman conf -s archiver.hyperkitty -k configuration
This will print the path to the mailman-hyperkitty configuration file.
Look in that file for the base_url: setting and verify that it has an https scheme.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan