Verification links to localhost

The verification link I get back when trying to add an account, referes to localhost, e.g.
To confirm this is correct, go to https://localhost:8000/accounts/confirm-email/Mw:1...
Where do I change that?
Thanks in advance, Lars

On Sun, Feb 5, 2023 at 9:51 AM Lars Bjørndal <lars@lamasti.net> wrote:
What do you have as POSTORIUS_TEMPLATE_BASE_URL value in settings?
-- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

Hi, and than you for your quick reply!
You wrote:
I don't have this variable anywhere in /etc/mailman3. However, I found it here:
./venv/lib/python3.10/site-packages/mailman_web/settings/mailman.py:POSTORIUS_TEMPLATE_BASE_URL = 'http://localhost:8000'
In which config file should that variable be set, and how do I set it so that mailman can works for multiple domains?
Thank you.
Lars

On Sun, Feb 5, 2023 at 10:23 AM Lars Bjørndal <lars@lamasti.net> wrote:
Because it is still too early in your quest to get to run Mailman3, I'd advise that you take your time to follow this guide: https://docs.mailman3.org/en/latest/install/virtualenv.html#
It is the official installation guide. There is a step where it tells you to create a file named settings.py, in a particular path. You really need that step.
Regarding your question about multiple domains, that is already well taken care of when you create a list either via Postorius or the cli: (venv) [mailman@gw /opt/mailman]$mailman create list1@domain1.name (venv) [mailman@gw /opt/mailman]$mailman create another-lis@domain2.name
Mailman will know how to handle this in conjunction with your MTA.
-- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

Hi!
You wrote:
It is the official installation guide.
Yes, I've followed it, maybe with some errors.
There is a step where it tells you to create a file named settings.py, in a particular path. You really need that step.
Yes, I have the file /etc/mailman3/settings.py, but in that file, I didn't have the variable in question.
That's right. But, still, when I set the SITE_ID = 0, I get an server error when trying to connect. I also get mail from Django that states the error. I'm not sure how to fix it.
Thanks, Lars
[...]

On Sun, Feb 5, 2023 at 2:16 PM Lars Bjørndal <lars@lamasti.net> wrote:
Oh, in that case, it does not appear in settings.py. I have followed that guide, but I always login to the /admin UI to create a site (and a mail domain tied to a site) before I create my lists. Perhaps that's why I haven't encountered the problem you are seeing.
How many sites did you create already?
IIRC, this SITE_ID = 0 should be accompanied with FILTER_VHOST = True
-- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

[Odhiambo] [...]
How many sites did you create already?
Two.
IIRC, this SITE_ID = 0 should be accompanied with FILTER_VHOST = True
Tried that too.
In the email from Django, I have:
Internal Server Error: /mailman3/lists/
DoesNotExist at /mailman3/lists/ Site matching query does not exist.
Request Method: GET Request URL: http://localhost:8000/mailman3/lists/ Django Version: 4.1.4 Python Executable: /opt/mailman3/venv/bin/python3
Lars

On 2/5/23 03:16, Lars Bjørndal wrote:
Yes, I have the file /etc/mailman3/settings.py, but in that file, I didn't have the variable in question.
That file contains overrides to the defaults that it imports from mailman_web/settings/base.py and mailman_web/settings/mailman.py, but that's where you would set POSTORIUS_TEMPLATE_BASE_URL to override the default.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

On 2/4/23 22:50, Lars Bjørndal wrote:
This message comes from Django allauth and is probably using what it thinks is the host that is doing the add. This is based on your web server configuration which I would need to see to be more specific. I suspect you are proxying requests to https://localhost:8000/ and you are missing a directive to pass the host. For Apache I think you want
ProxyPreserveHost On
and for nginx
proxy_set_header Host $host;
proxy_set_header X-Forwarded-For $remote_addr;
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
participants (3)
-
Lars Bjørndal
-
Mark Sapiro
-
Odhiambo Washington