I set up Discourse, activated my account email, why am I still constantly receiving account activation emails every so often? How to configure to solve this bug

[john10]

It’s still not working, how do I configure Discourse SSL to enable it?

[john10]

The email supports SSL

Why can’t SSL connect?

Is it not connecting?

[supermathie (Michael Brown)]

@john10

However, after that, it keeps resending

@john10

Job exception: Net::SMTPUnknownError
net-smtp-0.5.1/lib/net/smtp.rb:1036:in `check_response' 
net-smtp-0.5.1/lib/net/smtp.rb:1010:in `getok' 
net-smtp-0.5.1/lib/net/smtp.rb:986:in `quit' 
net-smtp-0.5.1/lib/net/smtp.rb:732:in `do_finish' 

Your authentication setup is correct, and the mail you’re receiving is the same job, over and over again.

Discourse gets through the whole mail sending process but after receiving an unknown response code it aborts, thinking the mail send failed.

But the mail server actually did accept the mail!

Since Discourse didn’t realise the send was actually successful, it reschedules the job over and over.

[john10]

I changed my email, configured START_TLS to true.
It’s normal now!!!
But disabling DISCOURSE_SMTP_ENABLE_START_TLS: false
and using SSL to test sending emails doesn’t work, why? How to configure Discourse to enable SSL?

[supermathie (Michael Brown)]

For port 587 you should using STARTTLS

[john10]

But disable DISCOURSE_SMTP_ENABLE_START_TLS: false

Port 465, using SSL, test sending emails fails, why? How to configure discourse to enable SSL

[supermathie (Michael Brown)]

Your configuration in this post, if it’s the same one that generated this traceback, is correct. Use that one (port 587, and STARTTLS).

Port 587 is for TLS encryption negotiated after the initial connection (STARTTLS), whereas
Port 465 is for TLS encryption at connect time (SSL/TLS).

But many providers (correctly) block port 465 because of historical reasons, so 587 is recommended.

[rui5man]

DISCOURSE_SMTP_PORT: 587

DISCOURSE_SMTP_ENABLE_START_TLS: true

This configuration problem still cannot be solved

[rui5man]

Let’s still use port 587, port 465 has many issues