Why Does Tableau’s SMTP Test Pass When Emails Still Fail?

Treat a Tableau SMTP test as evidence about the test it performed. Tableau’s tsm email test-smtp-connection attempts to connect to the SMTP server configured for Tableau Server and reports connection status and configuration details. It is not an end-to-end acceptance test for finance’s scheduled PDF.

Tableau gives a specific Postfix example: the connection succeeds without Tableau being configured for the TLS required by the mail server, but the message is rejected afterward. The tsm email command reference explicitly identifies that false-positive result. A green connection test is therefore a reason to inspect the next step, not to rule out the sending configuration.

Ask the Tableau and mail administrators to correlate the same scheduled occurrence. Retain its time and time zone, recipient, subject and recorded error. First establish that the report rendered; if generation failed, an SMTP test cannot diagnose that earlier failure. If the message was rejected, retain the mail system’s rejection reason.

The TSM command and configuration discussed here apply to Tableau Server. For a Tableau Cloud subscription, identify whether the site uses standard sending or custom SMTP and investigate that route with its administrator. Do not look for a TSM command on a Tableau Cloud site.

The administrator’s test and finance’s sales email may differ in more than one respect. Compare the actual settings rather than making several changes at once. That gives the next test a clear purpose and makes the correction reproducible.

Tableau Server’s SMTP setup supports STARTTLS. Have the administrator match the documented configuration to the mail server’s requirements and apply the required pending changes. Tableau notes that SMTP configuration requires a restart of its services, so a successful test of an earlier configuration does not verify unapplied changes. Use Tableau’s SMTP setup instructions for that administration task.

Tableau also documents a TLS-related case where Background Tasks for Non Extracts can indicate that subscriptions are being sent while the SMTP command fails. Read the recorded error and mail trace together. The subscription troubleshooting guide describes that limitation; the summary alone is not evidence of receipt.

If ATRS produces finance’s sales PDF, start with the account the job actually uses. Options > Messaging holds the default messaging configuration. In the schedule’s Email destination, inspect Mail Server because the job can select an added SMTP account instead of that default. A successful test of one account does not establish that a different selected account can send the report.

For a separately maintained SMTP account, go to System > SMTP Servers, add or review the intended configuration, and use Test. Supply the host, account, sender, port and other settings approved by the mail administrator. The ATRS multiple-server guide explains selecting that account in the destination.

Configure and test the account the report destination will use. The sample values shown are examples; use your mail administrator’s settings.

For Office 365 modern authentication, the ATRS messaging guide describes choosing Office 365 and the configured integration account, then using Test Settings. Choose the route required by your organization rather than transferring credentials from an unrelated test.

Next, use Tools > Test on the prepared report with a controlled destination. Inspect the PDF and the received message, then review the job’s result. This tests the report-and-destination combination that the account-only test did not establish. In System Monitor > History View, expand the run to distinguish generation from a failed destination; consult the History View guide.

If the schedule changes displayed sender details, check that the selected account is authorized to send that way. The Email destination guide cautions that sender customization can conflict with mail-server rules. Maintaining the correct account and message together is a practical reason to use a Tableau report scheduler for repeated report production.

For Tableau Server, an authorized administrator can use the documented connection check as one diagnostic input:

tsm email test-smtp-connection

Retain its connection status and configuration details with the actual subscription’s failure evidence. The command’s known TLS false-positive condition is why an application or operations dashboard should not convert that result into “finance received the report.” Verify the real subscription separately through the appropriate administration workflow.

If an application requests an ATRS job, preserve its original request reference, schedule and returned execution identifier. Inspect the result payload and each destination result. Keep any available mail-message or trace identifier alongside that record so the mail administrator can follow the same occurrence beyond the reporting application.

A reporting execution identifier and a mail trace identifier describe different systems. Map them in your application’s own record when the sending route exposes the necessary information; do not assume that an SMTP success response contains proof of mailbox delivery. Confirm the final document and reporting period with the receiving process.

After a lost response or uncertain send, reconcile history and the receiving system before repeating the job. A second request can duplicate a message already accepted. The ATRS Developer Hub documents execution tracking; use the selected mail provider’s trace for the separate mail handoff.

For finance’s sales PDF, close the issue only after the actual scheduled route produces a message that the intended reader receives and can open. Record which setting or policy caused the failure, the corrected configuration and the representative test result. Confirm that the next scheduled report still uses that route.

Native Tableau subscriptions remain suitable when their PNG/PDF delivery meets the need. Evaluate ATRS when recurring reporting also needs maintained sending accounts, message design, export settings or destination results. Its account test is a starting point; the full report handoff is the result to evaluate.

Explore ATRS report email design and sending

Evaluating recurring report email delivery? Share the guide with the colleagues responsible for deployment, report production and the sending account.

Download the ATRS Internal Evaluation Guide