Troubleshoot Office 365 SMTP Relay Response Delays
Question details
Identify why an Office 365 SMTP relay using an IP-based connector responds slowly or accepts messages inconsistently.

- Product
- Microsoft 365 Exchange Online SMTP relay
- Device & OS
- not provided
- Scenario
- An application sends messages through an IP-based SMTP relay connector, including messages addressed to invalid recipients.
- Observed behavior
- SMTP responses may be delayed, and messages may appear to be accepted inconsistently, especially when recipients are invalid.
Identify whether your mail environment is cloud-only, hybrid, or on-premises, and obtain access to the sending application's SMTP logs and the Exchange admin center. Record the sending public IP address, relay endpoint, message time, and affected recipient addresses.
Inspect SMTP responses and message delivery reports
Use SMTP logs and Exchange message trace to determine where the delay occurs and whether a message was accepted or later rejected.
Open the sending application's SMTP or relay logs and record the timestamps, commands, and server responses, especially for RCPT TO and DATA. Remove credentials and sensitive message content before sharing logs.
Open the sender's mailbox in Outlook or Outlook on the web and look for non-delivery reports around the time of the affected message. Note any diagnostic codes and recipient addresses.
In the Exchange admin center, open Mail flow > Message trace. Search using the sender, recipient, and time range, then review the message events and delivery status.
Send controlled test messages to a known valid recipient and an invalid recipient. Compare their SMTP responses, trace results, and any non-delivery reports.

Verify the IP connector and application timeout handling
Use this check when the SMTP conversation points to connection, connector, policy, or timeout issues.
Review SMTP Troubleshooting Reports with WPS Office
WPS Office is a free, lightweight alternative for reviewing troubleshooting documents and spreadsheets. Its familiar interface and Microsoft Office format support make it easy to move existing reports, but it does not fix Exchange Online SMTP relay issues.

Frequently Asked Questions
Why can an invalid recipient appear to be accepted by the SMTP relay?
Recipient validation can occur after the initial SMTP transaction. Check the response to RCPT TO and DATA, then look for a later non-delivery report in the sender's mailbox and run a message trace in the Exchange admin center.
Where can I check the IP address allowed by the connector?
In the Exchange admin center, open Mail flow > Connectors and inspect the connector used by the application. Compare its configured IP addresses with the public IP actually used to send mail.
Does a successful SMTP response mean the message was delivered?
Not necessarily. A successful response after DATA indicates acceptance for processing. Use Mail flow > Message trace in the Exchange admin center to check subsequent delivery events.
What should I do if the application times out waiting for a response?
Review the application's SMTP logs to identify the command awaiting a response. Configure appropriate connection and response timeouts in its SMTP settings or code, and handle temporary and permanent errors rather than assuming validation was skipped.




