New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Feature] Add support for Implicit TLS while sending email #2048
Comments
Sounds like we should just add code support for this: https://serverfault.com/questions/1064955/why-is-port-587-preferred-over-port-465-in-smtp |
Relevant RFC: https://datatracker.ietf.org/doc/html/rfc8314 The nomenclature here is "Implicit TLS". |
@EchedeyLR were you using the MTA/smarthost configuration option: Lines 414 to 419 in 3c59ce9
or direct mail sending? In the first case it's easy to add an |
If I'm reading RFC8314 correctly, it only applies to the first case (a message submission agent), not the second. |
I am using MTA in this case. |
And correct, implicit TLS is what I would like to use, which is the preferred way. |
Nice. Would you be able to test the patch in #2049? I backported it to a base of v2.11.1 so it won't make any irreversible changes to your database. You could build it from source with:
|
Let me see. I don't have GoLang installed on that machine nor at user level and would not want to mess the clean environment with it and having to clean later. I will see if I can build it in another machine and port it to the one executing it. |
Oh right, sorry, you can also get it here: https://irc.ergo.chat/.files/ergo_71871ca1ef01d6c5 |
Thank you. Give me a few hours and I will test it. |
It works: :3 Edited: I also confirm that I received the message through email properly. |
Currently Ergo doesn't support TLS-only connections for email sending.
It would be good if a note was added to the documentation to avoid confusion.
The text was updated successfully, but these errors were encountered: