On 3/22/21 1:03 PM, Johannes Rohr wrote:

In /etc/mailman3/mailman-web.py I have added  FILTER_VHOST = True so that only the list for the current domain are shown.

But this has no effect.

The current situation with Postorius >=1.3.3 and Hyperkitty >=1.3.3 is for HyperKitty, FILTER_VHOST = True works. For Postorius, it works only if in the domains view, each mail host has a unique web host. It doesn't work. See this post <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message/...> and others in that thread for more info.

Prior to Postorius 1.3.3 and Hyperkitty 1.3.3 it would only work if the mail host and web host values were identical for the domain.

What's more, in hyperkitty I see at the top left the lable for the default domain, even though I am visiting from another domain.

That has nothing to do with FILTER_VHOST. The displayed there is the site referenced in the SITE_ID setting.

The web domains are exactly the same as the mail domans (lists.[domain].[tld])

In that case, I'm not sure what's going on.

In the Nginx config I have added 

location / { proxy_set_header X-Forwarded-Proto $scheme; proxy_set_header X-Forwarded-Host $host; proxy_pass http://localhost:8000/; [....]

}

to make sure that mailman3 knows from which URL it is visited.

Am I overlooking something?

I am using the distribution packages on Ubuntu 20.04: mailman3 3.2.2-1 mailman3-web 0+20180916-10

I see, the mailman3-web package is quite dated. Is it recommended to install via virtualenv instead?

Yes, the issue is at least partially that that mailman3-web package doesn't have any of the FILTER_VHOST fixes.

And yes, if you don't want to be stuck with dated packages tha don't include recent fixes, we recommend installation as documented at <https://docs.mailman3.org/en/latest/install/virtualenv.html>

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