Troubleshoot an Office 365 SMTP Relay Multiple-Tenant Error
Question details
Identify the Office 365 mail submission method and locate SMTP logs to investigate a multiple-tenant relay error.

- Product
- Microsoft 365 Exchange Online
- Device & OS
- not provided
- Scenario
- An internal web server sends messages through an Office 365 custom mail connector.
- Observed behavior
- The server reports a 4.5.3 error stating that recipients belong to multiple tenants, although messages are delivered.
Record the affected message time, sender, recipients, and complete SMTP error text. Check whether the web application sends mail directly or passes it through an IIS SMTP service.
Identify the Submission Method and Review Mail Traces
Use connector settings and message traces to determine how the application sends mail and which recipients encounter the error.
Open the web application's mail configuration and record the SMTP host, port, authentication settings, and TLS or STARTTLS support. An authenticated connection to smtp.office365.com on port 587 typically indicates SMTP client submission; a connection to the tenant's MX endpoint on port 25 may indicate SMTP relay.
In the Exchange admin center, open Mail flow > Connectors. Review any connector from your organization's email server to Microsoft 365, including the public IP addresses or certificate used to identify the sending server.
In the Exchange admin center, open Mail flow > Message trace. Search using the sender, affected recipients, and message time, then review the status and events for each recipient.
Review the full SMTP response and any non-delivery report (NDR) available to the sender. Compare affected recipient domains and timestamps with the message trace; delivery to some recipients does not establish that every recipient was accepted.

Enable IIS SMTP Logging or Check the Application Log
Capture the SMTP conversation at the component that actually sends the message.
Evaluate SMTP Client Submission as an Alternative
Consider authenticated mailbox submission if the application supports the required security and authentication settings.
Document SMTP Troubleshooting with WPS Office
WPS Office is a free, lightweight Office alternative with a familiar interface for working with documents and spreadsheets. Its Microsoft Office format support makes it easy to move existing troubleshooting notes and reports, though it does not repair Exchange Online connectors.

Frequently Asked Questions
How can I tell whether the server uses SMTP relay or client submission?
Check the application's SMTP host, port, and authentication settings. Authenticated submission to smtp.office365.com on port 587 typically uses client submission; a connection to the tenant's MX endpoint on port 25 may use SMTP relay. Confirm the latter in Exchange admin center > Mail flow > Connectors.
Where are IIS SMTP logs stored?
In IIS 6.0 Manager, open the SMTP virtual server's Properties and check the logging settings on the General tab. The configured log directory may be under the server's LogFiles directory. If the application sends directly to Microsoft 365, check its own logs instead.
Why does the application report an error if some messages are delivered?
Delivery to some recipients does not necessarily mean all recipients were accepted. Compare the complete SMTP response with a message trace for each recipient in Exchange admin center > Mail flow > Message trace.
Can I switch the application to an Office 365 mailbox for sending?
Possibly. Check the application's SMTP settings for STARTTLS and a supported authentication method, and confirm that SMTP AUTH is allowed for the tenant and mailbox. If eligible, test smtp.office365.com on port 587 and verify the result with message trace.




