Steve wrote:
So we need to figure out where HyperKitty is getting its setting for MAILMAN_ARCHIVER_FROM.
- Are there multiple copies of settings_local.py lying around?
There only appears to be the one in /opt/mailman/mailman-suite/mailman-suite_project
- Does settings.py have "from settings_local import *" in it?
Yes. I assume that overrides the MAILMAN_ARCHIVER_FROM and other related settings defined at the top of the settings.py file? Or should I update settings.py based on what is in settings_local.py?
- Are there multiple copies of settings.py lying around?
Well, there are these:
./usr/local/lib/python3.8/site-packages/rest_framework/settings.py
./usr/local/lib/python3.8/site-packages/postorius/doc/settings.py
./usr/local/lib/python3.8/site-packages/django_q/tests/settings.py
./usr/local/lib/python3.8/site-packages/django_extensions/settings.py
./usr/local/lib/python3.8/site-packages/mailmanclient/restobjects/settings.py
./usr/local/lib/python3.8/site-packages/example_project/settings.py
Only the last has MAILMAN_ARCHIVER_FROM defined in it, but I was assuming from the example_project subdirectory name that this was just a sample file, and besides, "from settings_local import *" is also set in it.
- What else may have changed in the migration? Any software upgrades in mailman, hyperkitty, mailman-web (or wherever the settings*.py are coming from)?
So, I actually converted the instance to a template, copied and deployed to the new account. So, all the mailman, hyperkitty & nginx versions stayed the same.
Thanks for any assistance.
Pat Hirayama Pronouns: he/him/his Systems Engineer IT | Systems Engineering Fred Hutchinson Cancer Center O 206.667.4856 phirayam@fredhutch.org