logo
search
Exchange Connection Problems

Fix Microsoft 365 SMTP Relay Error 4.5.3: Recipients Belong to Multiple Tenants

Emma BrownEmma Brown Oct 7, 2026 868 views

Question details

The user needs to resolve an SMTP relay failure where emails are rejected because the transaction includes recipients in different Microsoft 365 tenants.

How to Fix Microsoft 365 SMTP Relay Error 4.5.3 (Recipients Belong to Multiple Tenants)
Product
Microsoft 365 Exchange Online
Device & OS
not provided
Scenario
Sending an email message through Microsoft 365 SMTP relay (Port 25) that includes both external recipients (in the To field) and internal recipients (in BCC).
Observed behavior
The server rejects the email, returning an 'Insufficient system storage' error with the response code '4.5.3 Recipients belong to multiple tenants'.
Before you start

Verify your organization's Exchange Online accepted domains and connectors, and ensure you have access to modify your application's SMTP sending logic.

Solution 1Recommended

Split the Message by Destination Tenant

Because Microsoft 365 SMTP direct relay natively restricts routing a single transaction across multiple tenants, separating the recipients into distinct messages is the most reliable resolution.

Exchange Online does not provide a tenant-level setting to override this security restriction for Port 25 direct send relays. The application generating the email must handle the recipient separation.

1
Modify Application Logic

Access the source code or mail configuration panel of the application generating the email.

2
Separate the Recipient Lists

Configure your mailing script to process internal (your verified domain) and external (different tenant) recipients in separate arrays.

3
Generate Distinct Transactions

Set the application to trigger a distinct SMTP send request for the external 'To' recipients, and a completely separate SMTP request for the internal 'BCC' recipients.

Split the Message by Destination Tenant
Free Microsoft Office alternative

Enhance Your Productivity with WPS Office

While resolving Exchange server configurations requires Microsoft 365 administrative access, you can handle all your daily document, spreadsheet, and presentation tasks seamlessly with WPS Office. It provides a lightweight, comprehensive productivity suite that requires no complex tenant configurations.

  1. 1. Download the Installer: Visit the official WPS Office website and click the free download button for your operating system.
  2. 2. Install the Software: Run the downloaded installation file and follow the simple on-screen instructions to set up the suite.
  3. 3. Open Your Documents: Launch WPS Office and immediately start opening, editing, and saving your existing Microsoft Office files without formatting loss.
Fully compatible with Microsoft Office formats including Word, Excel, and PowerPoint files.Lightweight application that uses minimal system resources while delivering high performance.Built-in PDF editing tools for easy document conversion and professional sharing.Familiar user interface ensuring a seamless migration for business teams.
microsoft office alternative - wps office

Frequently Asked Questions

Why does Microsoft 365 block SMTP direct relay to multiple tenants?

Microsoft imposes this restriction on Port 25 unauthenticated direct routing to prevent spam, unauthorized spoofing, and abuse of its server infrastructure. Allowing a single transaction to cross tenant boundaries poses a security risk.

Can I fix Error 4.5.3 by adding the external domain to my Exchange accepted domains?

No. You can only add domains to your accepted domains list if your organization actively owns and controls them. Adding an external company's domain is not possible or permitted.

Does this multi-tenant error happen when sending emails normally from Outlook?

Generally, no. Error 4.5.3 typically occurs only during unauthenticated SMTP relay (using Port 25) from background applications, scanners, or servers. Standard user emails sent via Outlook use authenticated client submission protocols.

What is the difference between direct send and SMTP client submission?

Direct send uses Port 25 and IP authentication to send emails strictly to recipients within your own organization. SMTP client submission uses Port 587 with mailbox credentials, allowing emails to be routed to internal and external recipients.