Hi Team, Using email service from godaddy and smtp ssl port 465 in config, but sending mail fails with Job exception: end of file reached. For me 465 works with email client such as thunderbird. What can be done to make email work with discourse on port 465. Running SMTP on other port such as 35…

Sendgrid use 587 too. Use 587 with starttls. TLS is effectively the successor to SSL.

This sounds like a problem with your mail provider or the server running Discourse (such as a firewall issue). It is not a problem with Discourse itself. Also note that port 465 hasn’t been for SMTPS for so long that the IETF has removed its registration as a well-known port. You should use port …

Hi Matt, I am able to telnet port 465 from discourse server and no firewall is configured for now. Email providers still supports 465 for secure connection for client which does not support STARTTLS. However that’s not the case here, so I can move to port 25 with STARTTLS on. Regards Manish

Sad to here this. My email service provider does not support for port 587.

Your ESP needs to be dragged, kicking and screaming, into the 21st century.

I have been googling for this, to see if I should use port 465 or not. Can you confirm as of 2018, if the recommended and safe settings is to use port 587 with STARTTLS (DISCOURSE_SMTP_ENABLE_START_TLS env for dockers) ? Sendgrid still offers port 465 “for SSL connections” as they say. I was think…

[Bild] mpalmer: Also note that port 465 hasn’t been for SMTPS for so long that the IETF has removed its registration as a well-known port. You should use port 25 or 587 with STARTTLS. There’s a January 2018 IETF RFC which recommends use of port 465 for “implicit” TLS. A motivation for this is…

Have there been any updates? My email provider also requires that the client automatically establish a TLS connection on connect on port 465. How do I tell Discourse to use this option? To be precise, in [swaks](https://linux.die.net/man/1/swaks) this is called --tlsc --tlsc, --tls-on-connect Ini…

I think the following is related: a never completed PR for Ruby’s action mailer describes how the action mailer needs to be configured. Specifically, the options tls and ssl need to be added. In Discourse, this could be in production.rb here PS: I submitted a PR with a proposed fix which can also…

Any practical solutions for sending e-mail over SMTPS on port 465? No, “change your ESP” , “use submission 587” and similar are not solutions to the problem in question :wink:

Practical solutions? No… it is quite common policy to force to use 587. So, what is the issue?

Sending email failed with SMTPS port 465

Support Self-hosting

djr013 29. September 2019 um 05:47 8

Es gibt eine IETF-RFC von Januar 2018, die die Verwendung von Port 465 für „implizites

Thema		Antworten	Aufrufe
Problem with SMTP configuration Self-hosting	13	7420	9. Februar 2022
Cannot send email - problem with port 465 Self-hosting email	9	4866	20. November 2022
SMTP email issue Net::Timeout Self-hosting	2	1643	18. Februar 2021
SSL/TLS for port 465 (Net::ReadTimeout) - undocumented solution Self-hosting email	2	823	11. November 2025
[fixed] Can not send the email Self-hosting	11	4577	16. Mai 2016

Sending email failed with SMTPS port 465

Verwandte Themen