I guess our email crossed each other. The joy of working in close time zones.

  Stephen J. Turnbull writes

> What will match with that prefix is determined by the content of the
> URLconf (../site-packages/mailman_web/urls.py). But you probably
> haven't touched that file (I didn't realize that was a Python module
> rather than the reference to a filesystem path).  Probably that file
> contains:
> 
> urlpatterns = [
>     path(
>         '',
>         RedirectView.as_view(url=reverse_lazy('list_index'), permanent=True),
>     ),
>     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),
>     # Include alternate Postorius and HyperKitty URLs.
>     path('postorius/', include('postorius.urls')),
>     path('hyperkitty/', include('hyperkitty.urls')),
> ]

  Yes, I installed this as /etc/mailman3/urls.py, and the salient
  parts are 

mailman@darni:~$ cat /etc/mailman3/urls.py | grep path\(\'
    path('postorius/', include('postorius.urls')),
    path('hyperkitty/', include('hyperkitty.urls')),
    path('mailman3/', include('postorius.urls')),
    path('archives/', include('hyperkitty.urls')),
    path('', include('django_mailman3.urls')),
    path('accounts/', include('allauth.urls')),
    path('accounts', include('allauth.urls')),
    path('admin/', admin.site.urls),

  So my fix is appending a second 'accounts' router *after* the one
  with the slash. Inserting it before does not fix. 

  The only thing I could imagine that leads to my mess is that I have a

RewriteRule "^/?$" "https://lists.repec.info/mailman3/lists/"; [R]

  Otherwise it shows me the "Debian Apache works" page. Further tests
  I have conducted now suggests that if I rewrite that rule as

RewriteRule "^/?$" "https://lists.repec.info/mailman3/lists/"; [END]

  this supposedly stops further processing of the request URL at that
  top point. Then the initial configuration works, and to answer your
  question, 

> What does "GET http://127.0.0.1:4386/accounts/confirm-email/"; respond
> with?  (Don't omit the trailing "/".)

root@darni ~ # GET http://127.0.0.1:4386/accounts/confirm-email/ | grep Verif
    Verify Your Email Address
        Verify Your Email Address

  It works.

  To make progress from this mess, I suggest to insert a suggestion
  to redirect the top level page into the documented apache
  configuration, something like

RewriteRule "^/?$" "https://lists.example.com/mailman3/lists/"; [END]

  So that apache non-wizards (like most of us) can use the provided
  sample more readly. 

  Thank you so much. I am now turning to my other mailman installation,
  the one had the Debian version installed before. More fun!

-- 
  Written by Thomas Krichel http://openlib.org/home/krichel on his 22211th day.
_______________________________________________
Mailman-users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/
Archived at: 
https://lists.mailman3.org/archives/list/[email protected]/message/UHR7NG4HHRHHZWJUNDIW2EBF3RPK6R6Z/

This message sent to [email protected]

Reply via email to