On 3/22/24 09:48, David Partain via Mailman-users wrote:
Right now, archiving is not working on the new installation, both building the archive on the new installation after the move and for new messages.
uwsgi-error.log is getting blasted with constant errors along the lines of what follows. I suspect that these errors are why archiving isn't working, but I obviously don't know that:
Message: BadSignature('Signature "ZWBXqQmWZwHTfa390lLIacpp8NQ" does not match')
I'm not sure if this is the issue with archiving or not.
What we have in our config files on the old installation and new installation are (the quotes are exactly as they are in the files): ... settings.py
SECRET_KEY = 'somerandomstringiaintputtinginmail' MAILMAN_ARCHIVER_KEY = 'somerandomstringiaintputtinginmail'
mailman-hyperkitty.cfg
api_key: somerandomstringiaintputtinginmail
All of that says that the value is the same for all three (whether I should have done so or not...) and those settings were carried along to the new installation as well.
See my reply at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message/...
As I say there, SECRET_KEY is not related in any way to MAILMAN_ARCHIVER_KEY and api_key. The latter two have to do with archiving and must match. The former is a Django thing and is completely separate.
At this point, put
SECRET_KEY_FALLBACKS = [
'F6V0Dr_SvBsx5-cY8vcvLXrX8tA',
'ZWBXqQmWZwHTfa390lLIacpp8NQ',
]
in your local Django settings file. If you continue to get BadSignature: Signature "..." does not match' errors, add those unmatched signatures to SECRET_KEY_FALLBACKS.
Once you are no longer seeing BadSignature errors, if archiving is still not working, report any errors you are seeing from Mailman's mailman.log and Django's log.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan