On 10/22/21 12:53 PM, Marco Marinello wrote:
Dear Mark,
had # pip freeze ... HyperKitty==1.3.5 ... mailman-hyperkitty==1.2.0 ...
and got the described behaviour. Downgraded to
HyperKitty @ https://gitlab.com/mailman/hyperkitty/-/archive/1.3.4/hyperkitty-1.3.4.zip mailman-hyperkitty @ https://gitlab.com/mailman/mailman-hyperkitty/-/archive/v1.1.0/mailman-hyper...
and now archiving works.
Actually, with HyperKitty==1.3.5 and mailman-hyperkitty <1.2.0, the message is not exactly as in this message's Subject:. It is 'The MAILMAN_ARCHIVER_KEY is now required to be sent over the Authorization HTTP header, you need to upgrade the mailman-hyperkitty package to 1.2.0 or newer.
Perhaps you paraphrased the message. If not, that exact message was not in any version of HyperKitty leading up to 1.3.5.
And with mailman-hyperkitty==1.2.0, it should work.
I see what pip freeze reported, but something was wrong somewhere because that combination should work and the 'The MAILMAN_ARCHIVER_KEY ...' message would only be logged with a version of mailman-hyperkitty <1.2.0.
Perhaps you did not realize you had to restart Mailman core and skipped that step. The mailman-hyperkitty module is imported by Mailman core, thus core needs to be restarted if it is changed.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan