On 12/22/21 7:29 PM, Mark Sapiro wrote:
On 12/22/21 6:20 PM, David Newman wrote:
Update: The above worked fine until MM3 informed a list owner of pending subscription requests, with a URL like this:
https://lists.example.com/mailman/admindb/listname
and that URL returned a 404 error.
This looks like a uwsgi issue as discussed at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/U... although that's with apache and not nginx so it may not be.
If I'm reading the thread correctly, it's Apache workarounds to an underlying Debian issue, so I agree it may not apply with nginx.
Adding a stanza for 'location /mailman/' to the nginx config above clears the 404 error, but Postorius returns "Page not found" with no entry in the web or MM3 logs, and a 200 OK in the Nginx logs.
I think the URL is supposed to go to the list page in Postorius. How to configure this so that list owners and moderators get a valid URL for list management?
I'm not sure what the solution is in this case, but a workaround would be to add
url(r'^mailman/', include('postorius.urls')),
to the urlpatterns list in urls.py.
There are 260 files named 'urls.py' under /opt/mailman, mostly for socialaccount stuff.
Where does that change go? All files? Or just this one:
/opt/mailman/venv/lib/python3.9/site-packages/postorius/urls.py
Or somewhere else?
Thanks again.
dn