I have the same problem, after the mailman3 installation had run some weeks flawless. Removing the trailing / did not help. Any ideas?

On 10/13/21 3:38 AM, eggert--- via Mailman-users wrote:

What's strange, my mailman-web is referred to by https://lists.tdl/mailman3/ this show the message as above: This page either doesn't exist, or it moved somewhere else. The links in that page refer to urls like: https://lists.tld/mailman/postorius/lists/ This URL does not exist, of course. Where is the mailman3 replaced by mailman? All my config files refer to mailman3.

How have you installed Mailman?

We usually use links like https://example.com/mailman3 and https://example.com/archives in docs for Postorius and HyperKitty respectively. These are the ones in urlpatterns in mailman-web/urls.py We have also used https://example.com/postorius and https://example.com/hyperkitty as alternatives. To enable these, you need to add

     url(r'^postorius/', include('postorius.urls')),
     url(r'^hyperkitty/', include('hyperkitty.urls')),

to the definition of urlpatterns in urls.py so it becomes something like

urlpatterns = [
     url(r'^$', RedirectView.as_view(
         url=reverse_lazy('list_index'),
         permanent=True)),
     url(r'^mailman3/', include('postorius.urls')),
     url(r'^archives/', include('hyperkitty.urls')),
     url(r'', include('django_mailman3.urls')),
     url(r'^accounts/', include('allauth.urls')),
     # Django admin
     url(r'^admin/', admin.site.urls),
     url(r'^postorius/', include('postorius.urls')),
     url(r'^hyperkitty/', include('hyperkitty.urls')),
]


However, that doesn't explain why your `mailman3` URLs get munged to 
`mailman`. That is apparently a uWSGI thing, and since I've never used 
uWSGI, only gunicorn and mod_wsgi, I can't help with that other than to 
suggest that you might have neglected to restart uWSGI after removing 
the trailing slash.

-- 
Mark Sapiro <mark@msapiro.net>        The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan

I type this URL into the browser: https://lists.tld/mailman3/postorius/lists/ In the apache access log I find: GET /mailman3/postorius/lists/ With DEBUG=True, the web site shows: Request Method: GET Request URL: https://lists.tld/mailman//postorius/lists/

Using the URLconf defined in urls, Django tried these URL patterns, in this order:

^$
^mailman3/
^postorius/
^hyperkitty/
^user-profile/delete$ [name='mm_user_account_delete']
^user-profile/$ [name='mm_user_profile']
^accounts/
^admin/

The current path, /postorius/lists/, didn't match any of these.

This is driving me crazy. What's more, when I completely remove the ProxyPass statements from the apache config, it does not make a difference. Somehow the wsgi is not working at all.

Thanks for the solution !

I use Debian 10 (Buster) and I have this problem too. Unfortunately, I didn't notice which update caused the problem. It was working in august 2020 when I configured Mailman3.

A new update in Debian 10 for apache2 relaxes the behaviour ... I haven't tested if reverting the syntax works but the new syntax described above is still working.

apache2 (2.4.38-3+deb10u7) buster-security; urgency=medium

  * Fix possible NULL dereference or SSRF in forward proxy configurations
    (CVE-2021-44224)
  * lua: improve error handling (Closes: CVE-2021-44790)
  * mod_proxy_uwsgi: Remove duplicate slashes at the beginning of PATH_INFO
    (relaxes the behaviour introduced by the CVE-2021-36160 fix)

 -- Yadd <yadd@debian.org>  Tue, 21 Dec 2021 17:50:43 +0100