配置 SMTP 安装程序
- 版本 ：2022.1 及更高版本
Tableau Server 可以向服务器管理员发送有关系统故障的电子邮件，并向服务器用户发送有关订阅视图和数据驱动警报的电子邮件。但是，首先，您需要配置 Tableau Server 用于发送电子邮件的 SMTP 服务器。配置 SMTP 后，完成配置通知的步骤（配置服务器事件通知），然后在启动或重新启动服务器时，它将触发电子邮件通知，确认您已正确设置通知。 配置 SMTP 需要重新启动 Tableau Server 服务。
安全软件
若要为 SMTP 启用和配置 TLS，必须按照本主题中所述使用 TSM CLI。Tableau Server 仅支持 STARTTLS（机会性或显式 TLS）。
如果您的组织不使用公共证书来验证 TLS 连接，则可以将私有证书上传到 Tableau Server 以验证受信任的连接。有关详细信息，请参阅 tsm 安全自定义证书添加命令。
您还可以通过禁用证书验证过程将 SMTP TLS 配置为仅加密。有关详细信息，请参阅下面的使用 TSM CLI 选项卡中的配置文件参考部分。
在浏览器中打开 TSM：
https://
单击配置选项卡上的通知，然后单击电子邮件服务器。
输入组织的 SMTP 配置信息：
输入配置信息后，单击保存挂起的更改。
单击页面顶部的挂起的更改：
单击应用更改并重新启动。
运行 以查看并验证连接配置。请参阅 tsm 电子邮件测试-smtp-连接。
tsm email test-smtp-connection
SMTP CLI 配置参考
下表列出了可用于通过 TSM CLI 配置 SMTP 的所有选项。
| 选择 | 描述 |
|---|---|
svcmonitor.notification.smtp.server | SMTP 服务器的地址。 例：
|
svcmonitor.notification.smtp.send_account | SMTP 帐户的用户名。 |
svcmonitor.notification.smtp.port | SMTP 服务器的端口号。默认值为 25。 |
svcmonitor.notification.smtp.password | SMTP 服务器帐户的密码。 例：
|
svcmonitor.notification.smtp.ssl_enabled | Specifies whether the connection to the SMTP server is encrypted. The default is false. |
svcmonitor.notification.smtp.ssl_required | If enabled, Tableau Server will refuse to connect to SMTP servers without using TLS. The option must also be set to true. The default is false. |
svcmonitor.notification.smtp.ssl_check_server_identity | If set to true, Tableau Server will check the SMTP server identity as specified by RFC 2595. These additional checks based on the content of the server's certificate are intended to prevent man-in-the-middle attacks. The default is false. |
svcmonitor.notification.smtp.ssl_trust_all_hosts | When using TLS, trust certificates from all mail servers, ignoring the validity of the certificate's chain of trust. By setting this key to true, TLS will be used only to encrypt the traffic to the SMTP host. The default is false. |
svcmonitor.notification.smtp.ssl_ciphers | The default and supported sets of cipher suites is defined by the version of JDK that is installed with Tableau Server. See the section below, TLS ciphers, for a list of supported and default ciphers. To update the cipher suites used by Tableau Server for SMTP TLS connections, enter a white space-separated list of cipher suites for this value. For example, . |
svcmonitor.notification.smtp.ssl_versions | The default TLS versions enabled on this version of Tableau Server are TLSv1, TLSv1.1, TLSv1.2 and TLSv1.3. TLS version support is defined by the version of JDK that is installed with Tableau Server. Supported versions of TLS are . To update the versions used by Tableau Server for SMTP TLS connections, enter a white space-separated list of versions for this value. For example, . |
svcmonitor.notification.smtp.from_address | Email address that will send an notification if there's a system failure. The email address must have valid syntax (for example, ITalerts@bigco.com or noreply@mycompany), but it does not have to be an actual email account on Tableau Server. (Some SMTP servers may require an actual email account, however.) Note: You can override the system-wide email address on a per-site basis. For more information, see What is a site. Example:
|
svcmonitor.notification.smtp.target_addresses | Email address to receive notifications. If email notifications are enabled, you need to include at least one address. Separate multiple addresses with commas. Example:
|
svcmonitor.notification.smtp.canonical_url | URL of the Tableau Server. Enter or , followed by the name or IP address of the Tableau server. Used in the footer of subscription email. http:// https://Example:
|
TLS ciphers
The following is a list of TLS ciphers that are supported by the JDK that is included with Tableau Server. In this version of Tableau Server, all of these ciphers are enabled by default. You can specify a custom list of ciphers for your SMTP configuration by entering a white-space separated list with the option, , as described in the table above.svcmonitor.notification.smtp.ssl_ciphers
TLS_RSA_WITH_AES_128_CBC_SHA256 | TLS_ECDH_RSA_WITH_AES_256_GCM_SHA384 |
TLS_DHE_DSS_WITH_AES_256_GCM_SHA384 | TLS_ECDH_RSA_WITH_AES_128_GCM_SHA256 |
TLS_ECDH_RSA_WITH_AES_256_CBC_SHA384 | TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA |
TLS_ECDH_ECDSA_WITH_AES_128_CBC_SHA | TLS_RSA_WITH_AES_256_CBC_SHA256 |
TLS_RSA_WITH_AES_128_GCM_SHA256 | TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384 |
| TLS_ECDH_RSA_WITH_AES_128_CBC_SHA256 | TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 |
TLS_DHE_DSS_WITH_AES_128_CBC_SHA256 | TLS_DHE_DSS_WITH_AES_256_CBC_SHA |
TLS_DHE_RSA_WITH_AES_128_CBC_SHA256 | TLS_DHE_RSA_WITH_AES_256_CBC_SHA256 |
TLS_RSA_WITH_AES_256_GCM_SHA384 | TLS_EMPTY_RENEGOTIATION_INFO_SCSV |
TLS_ECDH_ECDSA_WITH_AES_256_CBC_SHA384 | TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA |
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA | TLS_DHE_DSS_WITH_AES_256_CBC_SHA256 |
TLS_RSA_WITH_AES_256_CBC_SHA | TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256 |
TLS_ECDH_ECDSA_WITH_AES_128_CBC_SHA256 | TLS_DHE_RSA_WITH_AES_256_CBC_SHA |
TLS_DHE_DSS_WITH_AES_128_GCM_SHA256 | TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 |
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384 | TLS_ECDH_RSA_WITH_AES_128_CBC_SHA |
TLS_DHE_RSA_WITH_AES_256_GCM_SHA384 | TLS_DHE_RSA_WITH_AES_128_CBC_SHA |
| TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256 | TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA |
| TLS_DHE_RSA_WITH_AES_128_GCM_SHA256 | TLS_ECDH_ECDSA_WITH_AES_128_GCM_SHA256 |
| TLS_ECDH_RSA_WITH_AES_256_CBC_SHA | TLS_DHE_DSS_WITH_AES_128_CBC_SHA |
| TLS_ECDH_ECDSA_WITH_AES_256_CBC_SHA | TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 |
| TLS_RSA_WITH_AES_128_CBC_SHA | TLS_ECDH_ECDSA_WITH_AES_256_GCM_SHA384 |
| TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 | TLS_AES_256_GCM_SHA384 |
| TLS_AES_128_GCM_SHA256 |