Problems getting MM3 to work
I have been using mailman2 for some 15 years ... decided that it is time to upgrade to MM3. I have to admit that I am finding it very hard to do so. My target is a Rocky Linux machine (AKA CentOS/RedHat). I am doing a test install in a virtual Debian 10 machine - the idea is learn how it hangs together before reimplement on Rocky (where I tie things down with SELinux).
For me the biggest problem is the poor documentation - for someone who is new at MM3 and is not a Python programmer.
After a few false starts I am doing a virtualenv installation as described:
https://docs.mailman3.org/en/latest/install/virtualenv.html
(Changes: I am using mariadb not postgresql, apache not nginx)
I am trying to set up the WSGI server.
It thinks that my domain is example.com ... when I 'grep -r example.com /opt/mailman' I see 11338 lines - far too many to look through.
Could someone please tell me what/where I configure to enter my test domain.
Thanks in advance.
-- Alain Williams Linux/GNU Consultant - Mail systems, Web sites, Networking, Programmer, IT Lecturer. +44 (0) 787 668 0256 https://www.phcomp.co.uk/ Parliament Hill Computers Ltd. Registration Information: https://www.phcomp.co.uk/Contact.html #include <std_disclaimer.h>
On 4/24/23 8:18 AM, Alain D D Williams wrote:
It thinks that my domain is example.com ... when I 'grep -r example.com /opt/mailman' I see 11338 lines - far too many to look through.
Could someone please tell me what/where I configure to enter my test domain.
The Postorius Domains view will show you the SITE_ID for your domain.
In /etc/mailman3/settings.py you probably have
SITE_ID = 1
Change that to the value from the Postorius Domains view.
If you have more than one domain, you can set
SITE_ID = 0
and that should show the domain from the http request.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On 4/24/2023 5:11 PM, mailman-users-request@mailman3.org wrote:
The Postorius Domains view will show you the SITE_ID for your domain. In /etc/mailman3/settings.py you probably have SITE_ID = 1 Change that to the value from the Postorius Domains view. If you have more than one domain, you can set SITE_ID = 0 and that should show the domain from the http request.
Mark - I encountered the same problem and it wasn't clear from the documentation what to do about it.
So I eventually changed the name from example.com using the /admin link.
But if I now set SITE_ID = 0, and restart the server, it is not happy and tells me it encountered an error.
raise self.model.DoesNotExist(django.contrib.sites.models.Site.DoesNotExist: Site matching query does not exist.
I guess I should just let it be set to 1 and be done with it? - Mark
On 4/24/23 4:53 PM, Mark London wrote:
Mark - I encountered the same problem and it wasn't clear from the documentation what to do about it.
So I eventually changed the name from example.com using the /admin link.
But if I now set SITE_ID = 0, and restart the server, it is not happy and tells me it encountered an error.
raise self.model.DoesNotExist(django.contrib.sites.models.Site.DoesNotExist: Site matching query does not exist.
I'm not sure about this. It may only work if there is more than one site. On the other hand, it requires that the requesting domain match a site. I.e., I think if the site's domain is example.com, but the request is from www.example.com, that could cause it to fail.
Also, if proxying to a wsgi server, the web server has to pass the host. I.e., for nginx,
proxy_set_header Host $host
and for Apache
ProxyPreserveHost On
I guess I should just let it be set to 1 and be done with it? - Mark
Yes, I think so.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
participants (3)
-
Alain D D Williams -
Mark London -
Mark Sapiro