Hello, the ./discourse-setup bash script deosn’t populate DISCOURSE_SMTP_DOMAIN in the PUPS configuration file. I used rake admin:create inside the container, to find the following impact to GUI; [image] [image]

[изображение] Ethsim2: the ./discourse-setup bash script deosn’t populate DISCOURSE_SMTP_DOMAIN This variable sets the EHLO hostname used by the client during the SMTP conversation. Almost nobody needs it and it almost never matters what it’s set to. (I have encountered zero situations wher…

For a time it got populated with the host name, I’m pretty sure. But also, in most cases it doesn’t matter.

is there some regex we can use to extract the email domain from after the @ in DISCOURSE_NOTIFICATION_EMAIL understanding deployment cases where the email domain is different to the web domain. Something like: DISCOURSE_SMTP_DOMAIN=$(echo "$DISCOURSE_NOTIFICATION_EMAIL" | sed -E 's/^[^@]+@(.+)$/\…

[image] this was because DO block port 587, should have used 2525 - but not sure how this works with Brevo

Arguably it should default to port 2525 or suggest to people that most VMs block SMTP ports and most SMTP services allow on port 2525 (but that’s getting to be a lot of words)

[изображение] pfaffman: Arguably it should default to port 2525 The fact that Digital Ocean blocks port 587 is a terrible, uninformed decision with no basis in good practice. I’m surprised they haven’t started to block 2525 by default for the same reason.

[изображение] supermathie: The fact that Digital Ocean blocks port 587 is a terrible, uninformed decision with no basis in good practice. I don’t disagree. I’m pretty sure that they aren’t the only ones who do it (but I’m having trouble backing that up). What’s strange is that they’ve always …

[изображение] Ethsim2: this was because DO block port 587 How did you discover this? Did you try the emails:test rake task, and if you did was it useful? Did you know it existed?

Thanks, Michael - here’s what actually happened on today’s install and how I worked out that port 587 was the root cause. When I first ran ./discourse-doctor at 50:30 , it clearly showed that outbound SMTP on 587 was failing. There were no successful test emails anywhere in that part of the process.…

./discourse-setup не заполняет DISCOURSE_SMTP_DOMAIN

Поддержка Самостоятельное хостинг

pfaffman (Jay Pfaffman) 07.Декабрь.2025 12:48:52 2

В какой-то момент оно, кажется, заполнялось именем хоста. Но в большинстве случаев это не имеет значения.

Тема		Ответов	Просм.
Troubleshoot email on a new Discourse install Self-Hosting configuring , email , how-to	37	182799	27.04.2026
No activation email Self-hosting	11	1153	01.08.2022
Need help with SMTP settings from Brevo to Discourse Support	4	172	12.05.2025
Edit SMTP username Support	19	2696	16.11.2020
Cannot send mail with Discourse on new install but can from command line (on digital ocean) Self-hosting	8	2313	01.06.2020

./discourse-setup не заполняет DISCOURSE_SMTP_DOMAIN

Связанные темы