2 of 2 people found this helpful
Have the same issue after upgrading to 2018.3.0 on all ports 25, 465 & 587. Currently have a support case open.
The only option which worked was using the google restricted SMTP server "aspmx.l.google.com" on Port 25, as this does not rely on TLS. This is not a workable solution though as it will only send emails to Gmail or G-Suite users.
Having this same issue with GMAIL, as well as with Office365. When using port 465 error is cannot reach smtp port = -1; when using port 587 error is must issue starttls command. Cannot locate option for starttls
4 of 4 people found this helpful
Working with Tableau Support we ran the following script which appears to have fixed our issue for now. They did warn that this isn't officially supported and could break with future releases.
"TSM configuration set -k svcmonitor.notification.smtp.ssl_enabled -v true"
The comment worked but we have to run Tsm pending-changes apply command after that
Is it necessary to configure SSL for Tableau Server to send the subscriptions mail from gmail .Please respond on this issue.
I already have svcmonitor.notification.smtp.ssl_enabled set to true, but still cannot connect to SMTPS on 465. Can send an email from the same machine from the command line following this: Using the Command Line to Send Email Through the Amazon SES SMTP Interface - Amazon Simple Email Service so must be something on Tableau server that doesn't work.
Changed to 587 and it works.
Unfortunately, Tableau Server cannot use SSL with SMTP email servers. That is changing with a future release but I cannot advise which release yet. Tableau Server has never supported TLS or SSL when sending subscription notices. If your email server is SSL or TLS enabled, then you have to setup a proxy email server as an interim step. You install any open source SMTP server directly on Tableau Server and you set that up so it exchanges messages with Tableau Server unencrypted. Next you configure that proxy email server to resend all messages to your email server using SSL/TLS. Keep and eye on our prerelease site when we release a version that support SSL/TLS for SMTP connections.
See the notation on the Tableau Server CLI listing of installation options where it states encrypted messages are not supported officially:
This is likely to change with a future version post 2019.3 so stay tuned to http://prerelease.tableau.com
Thank you for the post. Could you confirm is 2019.3 supports TLS/SSL emails?
Notice the statement I said was POST-2019.3. It is now officially a part of 2019.4 for 4th quarter release of 2019. The beta site lets you test it right now. See prerelease.tableau.com
really looking forward to this release!
in the meantime a few things from this post might help others looking: https://medium.com/datadream/tableaugmail-3039ac90861d
I'll summarize that post here:
1. tableau send to smtp.gmail.com at port 587
2. tsm configuration set --key svcmonitor.notification.smtp.ssl_enabled --value true
3. gmail "less secure apps" enabled
4. gmail 2-factor auth disabled.
Tableau really needs a "send test email" button. Please upvote this feature at: https://community.tableau.com/ideas/3335
Troubleshooting smtp problems was made easier by tail/grep the backgrounder_node logs:
grep smtp /var/opt/tableau/tableau_server/data/tabsvc/logs/backgrounder/backgrounder_node1–1.log
The test button is there in 2019.4 and it is scheduled for release the week before TC19 (November, 2019)!!!
Only a few weeks away and it will be live!
No, you can use the tsm command posted here as the solution until you can upgrade to 2019.4. Understand with 2019.4 this won't be necessary as port 587 and encrypted email will be supported.
Official support for encrypted SMTP will be in 2019.4 and it is in the beta. I'm pretty certain it will be released in November. For those that cannot upgrade to 2019.4, the solution posted works but it is not officially supported. Tableau Support provided this work around until 2019.4 customers can upgrade over time. Generally, Port 587 is the encrypted port for email traffic so I think you have to use that port .