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 where it matt…

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 sort-of d…

[画像] 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 を設定しない

サポートインストール

supermathie (Michael Brown) 2025 年 12 月 7 日午後 9:05 7

Digital Oceanがポート587をブロックしているという事実は、良い慣行に基づかないひどい、情報に基づかない決定です。

同じ理由で2525もデフォルトでブロックし始めないことに驚いています。

トピック		返信	表示
Troubleshoot email on a new Discourse install Self-Hosting email , configuring , how-to	36	183168	2026 年 4 月 27 日
No activation email Self-hosting	10	1158	2022 年 8 月 1 日
Need help with SMTP settings from Brevo to Discourse Support	3	177	2025 年 5 月 12 日
Edit SMTP username Support	19	2722	2020 年 11 月 16 日
Cannot send mail with Discourse on new install but can from command line (on digital ocean) Self-hosting	8	2323	2020 年 6 月 1 日

./discourse-setup が DISCOURSE_SMTP_DOMAIN を設定しない

関連トピック