On May 11, 2021, at 1:18 PM, Mark Sapiro <mark@msapiro.net> wrote:
Set base_url: in /usr/local/mailman3/mailman-hyperkitty.cfg to a url that will reliably access HyperKitty, probably the same base URL that a user with a web browser would use.
Thanks Mark,
I really appreciate your assistance. New messages are now being archived as expected, but I still have a few small remaining issues to work out with my MM3 installation:
- some emails that arrived before I got the archive working are still sitting in:
/usr/local/mailman3/mm/var/archives/prototype/[listname]@[domain]/new
Strangely this includes at least one email that was archived. Should this directly be cleared as messages are archived? Is there a way to force it to be cleared?
- Some messages that arrived while I was having other problems with the setup have been stored in:
/usr/local/mailman3/mm/var/queue/shunt
What should I do to get these messages processed?
- Similar to above, some messages are in:
/usr/local/mailman3/mm/var/queue/bad
How can I get these messages processed?
4 Modified the template for “list:admin:action:post” through Postorious and emails that arrived after that were put in the “shunt” queue. I traced this problem to POSTORIUS_TEMPLATE_BASE_URL. By default, it is set to "http://localhost:8000 <http://localhost:8000/>” which is where uwsgi is listening. However, uwsigi is listening for uwsgi:/ not http://. Should I change POSTORIUS_TEMPLATE_BASE_URL to “uwsgi://localhost:8000 <uwsgi://localhost:8000>” or keep http but make it something else?
Thanks again for any help anyone can provide.
Jeff