On 4/11/19 6:40 PM, brian@emwd.com wrote:
Also Kelly are you sure this is correct:
"There are two configuration files that have a key in them that must match for Hyperhitty to authorize and be able to store archives (the paths should be as follows): /etc/mailman3/mailman-hyperkitty.cfg (set the api_key without any quotes) /etc/mailman3/mailman-web.py (set the ‘SECRET_KEY’ - include single quotes around the key)"
It was the MAILMAN_ARCHIVER_KEY that I needed to make sure it was being matched by the API key in mailman-hyperkitty.cfg. I believe the SECRET_KEY setting has nothing to do with the auth errors that Hyperkitty was displaying.
Yes. SECRET_KEY is used internally within Django. See <https://docs.djangoproject.com/en/2.1/ref/settings/#secret-key>. It is the MAILMAN_ARCHIVER_KEY setting that must match the api_key setting in mailman-hyperkitty.cfg (modulo quoting).
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan