Edit, i figured it out in the yaml file the quotes around some of the entries were stopping from being read. this is what i used , DISCOURSE_SMTP_ADDRESS: mail.the DISCOURSE_SMTP_PORT: 465 DISCOURSE_SMTP_USER_NAME: accounts-no-reply@ DISCOURSE_SMTP_PASSWORD: X DISCOURSE_SMTP_ENABLE_START_TLS: …

the mail is running on a clients website server i access via cpannel, pretty sure it uses sendmail on linux. really no reason i should need port 25 for smtp i think. thats if you’re hosting your own mail service. not smtp. no matter what i change it to in the yml, it always just tries to use port 25…

i was told if you try to outbound over port 25 your IP is blacklisted immediately i’m not sure is this standalone.yml part of an advanced-setup

Yeah the standalone.yml is for if you have to use a non standard port and proxy on your webserver. For example I have it running on 127.0.0.1:3000 and nginx proxies it to 443 because I have 6 websites running on the same server so nginx can have many websites on the same IP address. discourse_docker…

Running a build on standalone.yml

Product Support

NateDhaliwal (Nate Dhaliwal) June 20, 2025, 2:16pm 2

Hi there, what SMTP provider are you using? Also, have you tried changing ports to 2525 or 587?

Topic		Replies	Views
[fixed] Can not send the email Self-hosting	11	4603	May 16, 2016
Discourse with other websites, SMTP issue: End of file reached Self-hosting	7	2563	September 22, 2020
Problem with SMTP configuration Self-hosting	13	7471	February 9, 2022
Cannot send mail with Discourse on new install but can from command line (on digital ocean) Self-hosting	8	2443	June 1, 2020
Email connection using port 25, rather than default 587 Bug	7	1043	September 18, 2022

Running a build on standalone.yml

Related topics