SMTP Settings for Titan Mail Not Working

Product Support

AI-generated summary

A user, becl, reports that SMTP settings for Titan Mail are not working on their Discourse installation, despite trying various configurations. They provide their app.yml settings, including port 465 and 587 with different authentication options, but emails fail to send, resulting in a Net::ReadTimeout error. NateDhaliwal suggests trying port 587, which becl confirms did not work. supermathie asks if the issue is specific to the container, noting that the user’s manual test via swaks works on the host. becl later resolves the issue by using port 587 with ENABLE_START_TLS enabled and removing the AUTHENTICATION setting, acknowledging that stress may have led to configuration errors.

1

Hi,

I have installed Discourse on a standalone server and use Titan Email as my email provider.

I have spend all day searching the community and tried every varitation I can think of with the settings but emails still won’t send.

These are my settings.

## TODO: The SMTP mail server used to validate new accounts and send notifications
  # SMTP ADDRESS, username, and password are required
  # WARNING the char '#' in SMTP password can cause problems!
  DISCOURSE_SMTP_ADDRESS: smtp.titan.email
  DISCOURSE_SMTP_PORT: 465
  DISCOURSE_SMTP_USER_NAME: hello@mydomain.com
  DISCOURSE_SMTP_PASSWORD: mypass
  #DISCOURSE_SMTP_ENABLE_START_TLS: true
  DISCOURSE_SMTP_AUTHENTICATION: plain
  #DISCOURSE_SMTP_DOMAIN: community.mydomian.com
  DISCOURSE_NOTIFICATION_EMAIL: hello@mydomain.com

Can anyone help me figure out where I am going wrong?

2

Does it work if you change the port to 587?

3

No unfortunately. I had 587 with Enable start TLS on and commented out, neither worked.

I should have also posted this which is the error when I run Discord Doctor

======================================== ERROR ========================================
UNEXPECTED ERROR

Net::ReadTimeout

====================================== SOLUTION =======================================
This is not a common error. No recommended solution exists!

Please report the exact error message above to https://meta.discourse.org/
(And a solution, if you find one!)

Replacing: SMTP_PASSWORD
Replacing: LETSENCRYPT_ACCOUNT_EMAIL
Replacing: DEVELOPER_EMAILS
Replacing: DISCOURSE_DB_PASSWORD
Replacing: Sending mail to

4

I also ran this from the command line and it works, which is why I think there is something with the settings in app.yml that aren’t right.

swaks --to bec@.com --from hello@.com --server smtp.titan.email --port 587 --auth-user hello@****.com --auth-password “mypass” --tls

5

On the host?

Does it work on the host but fail in the container?

In any case, try doing it by hand and see how far you get.

6

Finally working changed it to 587 with ENABLE_START_TLS true and commented out #DISCOURSE_SMTP_AUTHENTICATION: plain

I was sure I had tried this at some point today. Perhaps I put the port number back to front or forgot to rebuild discourse in between. The moral don’t do things when you are tired and stressed!