On May 10, 2021, at 7:38 AM, Jeff <mm3@steele.com> wrote:
After using Mailman 2 (and possibly 1 though I don’t remember) for almost 20 years, I have just upgraded to Mailman 3. I followed the instructions here:
https://docs.mailman3.org/en/latest/install/virtualenv.html#virtualenv-insta...
Things generally work, but I have run into a couple of small problems:
- The uwsgi-error.log is filling with errors that seem to culminate in "ModuleNotFoundError: No module named ‘settings’”. My settings.py is located in “/etc/mailman3” and seems to be found by other components of MM3. This error must be coming from the cron jobs. Does anyone have any ideas how to fix this problem?
I replied to another message on the list with the same issue, lets discuss it over there since it looks very similar.
- While old messages were imported without issue, new emails are not being archives. I see them in:
mailman3/mm/var/archives/prototype/[listname]@[domain]/new
But they are not being delivered. I have added this to my mailman.cfg:
[archiver.hyperkitty] class: mailman_hyperkitty.Archiver enable: yes configuration: /usr/local/mailman3/mailman-hyperkitty.cfg
And created the "/usr/local/mailman3/mailman-hyperkitty.cfg” as such:
base_url: http://localhost/archives/ api_key: [key that matches “MAILMAN_ARCHIVER_KEY” in my settings.py]
Some documentation says that the url should be "http://localhost/hyperkitty/“, but url generates a page not found error on my setup while the archives are available at the “archives” url.
Are you seeing any errors in the logs?
Mailman Core’s logs are at /opt/mailman/mm/var/logs/mailman.log.
You should also check if this is something wrong at the Archiver end,
and the logs for those are available at /opt/mailman/web/logs/mailmanweb.log.
-- thanks, Abhilash Raj (maxking)