Send & Receive Issues

Why Exchange Online Message Trace Shows Out-of-Office Replies as Failed and Delivered

Olivia MillerOlivia Miller Nov 22, 2026 868 views

Question details

Understand why Exchange Online message trace shows both failed and delivered out-of-office activity when the recipient receives an automatic reply.

Product
Exchange Online
Device & OS
not provided
Scenario
An administrator is reviewing message trace results for organizational out-of-office automatic replies.
Observed behavior
The trace shows failed and delivered activity, including a failure reason containing resolver.oof.inttoext, while recipients receive an automatic reply.
Before you start

Have the affected mailbox address, recipient address, and approximate time of the automatic reply available. You need permission to view message traces and, if reviewing remote domains, access Exchange Online PowerShell.

Solution 1Recommended

Compare the Failed and Delivered Out-of-Office Trace Events

Use message trace details to determine whether a delivered reply and a suppressed duplicate account for the different statuses.

Exchange can generate more than one out-of-office response for an interaction and suppress a duplicate. In that case, one event may be delivered while another is marked failed. The trace details should be checked before assuming that every failure is a duplicate.

1
Find the trace results

In the Exchange admin center, open Mail flow > Message trace and search around the time of the automatic reply using the affected addresses.

2
Inspect both events

Open the failed and delivered results and compare their timestamps, sender and recipient addresses, message identifiers, and event details. Check the failed event for resolver.oof.inttoext.

3
Confirm delivery

Ask the recipient to check their inbox for the automatic reply and compare its timing with the delivered trace event. If the expected reply arrived, the failed event may represent a suppressed duplicate rather than a delivery failure.

Compare the Failed and Delivered Out-of-Office Trace Events
Investigate missing replies separately: If the recipient did not receive the expected reply, use the full trace details and the applicable automatic-reply settings to investigate further; a failed status alone does not establish the cause.
Free Microsoft Office alternative

Use WPS Office to Document Exchange Troubleshooting

WPS Office is a free, lightweight alternative for documenting trace findings and sharing troubleshooting notes. Its familiar interface and Microsoft Office format compatibility make it easy to move existing files; it does not change Exchange Online message delivery or trace results.

Record message trace findings and troubleshooting steps in WriterOpen and edit Microsoft Word DOCX and Excel XLSX filesUse a familiar interface for a smoother transition from Microsoft OfficeWork with a free, lightweight office suite
microsoft office alternative - wps office

Frequently Asked Questions

Does a failed trace event mean the out-of-office reply was not delivered?

Not necessarily. Exchange may suppress a duplicate while delivering another reply. Open both results in Exchange admin center > Mail flow > Message trace and confirm receipt with the recipient.

What does resolver.oof.inttoext tell me?

It is a reason reported in the failed trace event. Review the full event details, the recipient type, and related delivered events before deciding whether the result indicates a duplicate or a configuration issue.

Where can I check external out-of-office settings?

Connect to Exchange Online PowerShell and run Get-RemoteDomain | Format-Table Name,DomainName,AllowedOOFType,AutoReplyEnabled. Review the settings for the remote domain that applies to the external recipient.

Should I set AllowedOOFType to ExternalLegacy or enable TNEF?

Not automatically. Review the applicable remote-domain policy and your organization's requirements before changing AllowedOOFType. Enabling TNEF is not a general fix for this trace result.