[GH-ISSUE #3] Explicit SSL is not supported #3

Closed
opened 2026-09-29 12:58:29 +00:00 by slurdge · 6 comments
Owner

Originally created by @Raucev on GitHub (Feb 15, 2021).
Original GitHub issue: https://github.com/slurdge/goeland/issues/3

Originally assigned to: @slurdge on GitHub.

Hello! Any plans on SSL/TLS support for smtp servers? I've tried a couple of servers(Google, yandex, mail ru) and all of them don't work supossedly because of lack of encryption(ERR conn timed out). Would be nice to be able to toggle SSL usage via config file.

Originally created by @Raucev on GitHub (Feb 15, 2021). Original GitHub issue: https://github.com/slurdge/goeland/issues/3 Originally assigned to: @slurdge on GitHub. Hello! Any plans on SSL/TLS support for smtp servers? I've tried a couple of servers(Google, yandex, mail ru) and all of them don't work supossedly because of lack of encryption(ERR conn timed out). Would be nice to be able to toggle SSL usage via config file.
slurdge 2026-09-29 12:58:29 +00:00
Author
Owner

@slurdge commented on GitHub (Feb 15, 2021):

Hello,

I'm currently using it with a TLS smtp server, so it should work out of the box. SSL is different though. Are you using it with a configuration that would require explicit SSL ?

<!-- gh-comment-id:779227900 --> @slurdge commented on GitHub (Feb 15, 2021): Hello, I'm currently using it with a TLS smtp server, so it should work out of the box. SSL is different though. Are you using it with a configuration that would require explicit SSL ?
Author
Owner

@Raucev commented on GitHub (Feb 15, 2021):

Yes, most of the mail providers I've tried use 465 port for smtp with SSL enabled, but I've finally managed to make it work via google's TLS (587 port), thanks. Maybe it will help someone in the future.

<!-- gh-comment-id:779266439 --> @Raucev commented on GitHub (Feb 15, 2021): Yes, most of the mail providers I've tried use 465 port for smtp with SSL enabled, but I've finally managed to make it work via google's TLS (587 port), thanks. Maybe it will help someone in the future.
Author
Owner

@slurdge commented on GitHub (Feb 15, 2021):

Thanks for the report. I think this caused by https://github.com/jordan-wright/email/issues/77 and I'll try to find a fix.

<!-- gh-comment-id:779379575 --> @slurdge commented on GitHub (Feb 15, 2021): Thanks for the report. I think this caused by https://github.com/jordan-wright/email/issues/77 and I'll try to find a fix.
Author
Owner

@slurdge commented on GitHub (Oct 30, 2021):

I have changed the email package, I'll work next on enabling all SSL/TLS scenarios even with invalid certificates

<!-- gh-comment-id:955464608 --> @slurdge commented on GitHub (Oct 30, 2021): I have changed the email package, I'll work next on enabling all SSL/TLS scenarios even with invalid certificates
Author
Owner

@Raucev commented on GitHub (Oct 31, 2021):

Thanks

<!-- gh-comment-id:955731877 --> @Raucev commented on GitHub (Oct 31, 2021): Thanks
Author
Owner

@slurdge commented on GitHub (Oct 31, 2021):

Fixed in 0.8.0, but wait for 0.8.1, formatting is better on GMail.

<!-- gh-comment-id:955739045 --> @slurdge commented on GitHub (Oct 31, 2021): Fixed in 0.8.0, but wait for 0.8.1, formatting is better on GMail.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: slurdge/goeland#3
No description provided.