Stephen J. Turnbull writes
(Note: I usually copy that file to /etc/mailman3/urls.py in case I make changes. In particular I usually comment out the ^postorius and ^hyperkitty routes.) But in your case, I don't know what's in
| Using the URLconf defined in <code>mailman_web.urls</code>,
You have to tell us what's in that file.
I only now understand that this file is in fact
root@darni:/usr/local/mailman/venv/lib/python3.13/site-packages/mailman_web/urls.py
root@darni ~ # ls -l /usr/local/mailman/venv/lib/python3.13/site-packages/mailman_web/urls.py -rw-rw-r-- 1 mailman mailman 1559 Mar 18 08:25 /usr/local/mailman/venv/lib/python3.13/site-packages/mailman_web/urls.py
root@darni ~ # md5sum /usr/local/mailman/venv/lib/python3.13/site-packages/mailman_web/urls.py f382f0bc9cea1277c70226b45cf86def /usr/local/mailman/venv/lib/python3.13/site-packages/mailman_web/urls.py
I strongly suspect the file is the original file I got from pipping the package.
root@darni ~ # cat /usr/local/mailman/venv/lib/python3.13/site-packages/mailman_web/urls.py | grep -v ^#
from django.conf.urls import include from django.contrib import admin from django.urls import path, reverse_lazy from django.views.generic import RedirectView
urlpatterns = [ path( '', RedirectView.as_view(url=reverse_lazy('list_index'), permanent=True), ), # Include alternate Postorius and HyperKitty URLs. path('postorius/', include('postorius.urls')), path('hyperkitty/', include('hyperkitty.urls')), # Order counts for various links. Put the above first and the following # after so the suggested Apache config still works. path('mailman3/', include('postorius.urls')), path('archives/', include('hyperkitty.urls')), path('', include('django_mailman3.urls')), path('accounts/', include('allauth.urls')), path('admin/', admin.site.urls), ]
ok, I tested your approach, even though I don't know what the ... I am doing, Copying not
mailman@darni:~/venv/lib/python3.13/site-packages/postorius/urls.py
but
mailman@darni:~/venv/lib/python3.13/site-packages/mailman_web/urls.py
following guidance of Mark gleaned from
https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/V...
and added
ROOT_URLCONF='urls'
to
/etc/mailman3/settings.py
I can test. The obvious way is to add a route for acocunts. This can be done as an additional line
path('accounts', include('allauth.urls')),
There are two cases. If I place that line *after* the line
path('accounts/', include('allauth.urls')),
then on clicking the sign-in button, I get a redirect to
https://lists.repec.info/accountslogin/?next=/mailman3/lists/
which 404s. This may give the experts an addition hint where the problem is coming from. Placing
path('accounts', include('allauth.urls')),
*before*
path('accounts/', include('allauth.urls')),
seems to finally work, I can login! On the command line
mailman@darni:~$ GET http://localhost:4386/accounts/
works and
mailman@darni:~$ GET http://localhost:4386/accounts
fails.
My problem seems to be that I have to customize the installation, even though I have tried as much as I can not to, because the files as pipped seem not to work for me, for reason none of us seems to understand.
Cheers to all!
-- Written by Thomas Krichel http://openlib.org/home/krichel on his 22210th day.