Why Does the Tableau SMTP Test Pass When Report Emails Fail?

The tsm email reference says test-smtp-connection establishes a connection and reports its status and configuration. Its Postfix example succeeds at that stage but later rejects the email when TLS is required and Tableau Server is not configured to use it.

Tableau’s Server troubleshooting guide also describes an SMTP command error where Background Tasks for Non Extracts can still indicate sending. Keep the detailed error with the incident rather than closing it on that summary.

TSM is a Tableau Server administration tool. For Tableau Cloud, identify whether the subscription uses standard sending or custom SMTP and investigate that route with the site administrator. ATRS connects to Tableau Cloud only; it does not change Tableau Server’s SMTP settings.

Use Tableau’s SMTP setup guide when the actual error identifies a Tableau Server transport mismatch. It documents STARTTLS support and requires a restart of Tableau Server services when SMTP configuration is changed. Have the administrator match the mail service’s requirements and retest the report after applying the change.

Check any site-specific sender override as well as the system-wide address. Changing a displayed From address does not grant permission to send as that identity.

For Tableau Cloud attachments, the subscription troubleshooting guide documents a 2 MB maximum email size for standard sending and 10 MB with custom SMTP. These are email-size limits, so compare the complete message. Separate sending and receiving services may impose their own limits.

If the message was accepted but is missing from the inbox, use the mail administrator’s trace and receiving-system evidence. Report generation, mail submission and mailbox receipt are separate outcomes.

The Email destination guide covers HTML/text messages, subject/body inserts, To/CC/BCC and addresses from address books, database queries or text mailing lists. For embedded reports, enable Include Attachment when a file should accompany the body; embedding alone does not add one.

Use configured sending accounts rather than assuming sender customization is authorized. The Messaging options include re-sending failed emails. Review successful destinations and the existing message state before a manual retry so recovery does not create duplicate deliveries.

The History View guide shows how to expand partial successes and identify failed reports or destinations. Retain that evidence with the mail investigation.

If finance needs Excel, the Excel options include tab names, passwords, file properties and naming. Excel Data Only adds template placement, selected totals, reusable styles and typed column formats. Packages can merge Excel or PDF outputs or send several attachments; ZIP and configured PGP add protection where required. Test the finished message against mail limits and confirm the recipient can open it.

Use the ATRS execution guide. This example runs an existing ordinary single-report schedule. Replace 101 with its actual UniqueId, use your ATRS HTTPS address and keep the bearer token on a backend that authorizes the report request.

POST /api/Schedule/ExecuteScheduleAsync
Authorization: Bearer <ATRS-access-token>
Content-Type: application/json

{
  "ScheduleType": "report",
  "UniqueId": 101,
  "RunBy": "Finance application"
}

GET /api/Schedule/GetExecutionStatus?ExecutionId=<returned-id>
Authorization: Bearer <ATRS-access-token>

Save ExecutionId with the request time and intended reporting job. Monitor within a defined limit and parse the JSON-encoded ResultJson. Completed can contain Result=false; retain any error details and inspect report/destination results before requesting another copy.

If reporting succeeds but finance still has no message, follow the selected sending route with the mail administrator. Store a provider trace reference separately when one is available. Do not assume the ATRS response contains every downstream mail event or proves the report was read.

This payload uses saved outputs and destinations. It does not alter Tableau Server SMTP or supply new recipients. If submission times out, reconcile earlier execution activity and destination evidence before retrying, because work may already have started.