About this article: This article is reviewed against the cited sources. This is source research, not lab validation. Check the stated versions and your own requirements before making changes.
The bounce reads #550 4.4.7 QUEUE.Expired; message expired ##. Microsoft's page describes error 4.4.7 as "a persistent transient failure that occurs when Exchange Online can't deliver a message after repeated attempts and the message eventually expires in the queue." The sender sees the bounce only after 24 hours of failed attempts, so the mail has been stuck for a day by the time the message arrives.
First decide the scope. If only one recipient domain bounces, Microsoft says the problem is likely with that destination domain. If the destination's admins find nothing wrong on their side, Microsoft points to your own organisation: SPF, domain registration, hybrid routing, or duplicate recipients in your directory.
What the error means
Microsoft's page explains the mechanism. When Exchange Online attempts delivery, the destination can be unable or unwilling to accept the message. That produces a temporary 4.x.x code from the destination server, not a permanent 5.x.x rejection. Exchange Online "repeatedly tries to deliver the message over 24 hours. Only after 24 hours of unsuccessful delivery attempts does a recipient receive this NDR."
Microsoft's NDR overview describes 4.4.7 as "Message expired": the message in the queue expired before the action completed, and the code can also indicate that a message header limit was reached on a remote server or another protocol timeout occurred. It says the message "usually indicates an issue on the receiving server", so check the recipient address and whether the receiving server accepts messages.
The NDR for this error can carry two sections. The user section reads: "The server tries to deliver this message but can't. It stops trying. Try sending this message again. If the problem continues, contact your help desk." The administrator section reads #550 4.4.7 QUEUE.Expired; message expired ##, and Microsoft explains it as the rejecting system considering the message too old, either because it stayed on that host too long or because the sender's time-to-live was exceeded.
A third form carries 450 4.7.0 Proxy session setup failed on Frontend with '451 4.4.0 Primary target IP address responded with .... Microsoft says to record the error that follows that string and the last end point attempted.
Likely causes
| Cause | What you see | How to confirm |
|---|---|---|
| The destination mail server is offline, unreachable, or will not accept the message | One recipient domain bounces; others deliver | Contact the recipient with the server name and error from the NDR |
| The destination domain's MX record is missing or incorrect | One domain; mail never connects | Microsoft says the destination admin can test the MX record with the Outbound SMTP Email test in the Microsoft Remote Connectivity Analyzer |
| A network problem causes delivery to time out | The proxy-session text in the NDR names an end point | Record the end point the NDR names |
| Your SPF record omits a mail source | Wider failures, not one domain | Compare the SPF TXT record with every source that sends for the domain |
| Your domain has expired for non-payment | All external mail from the domain | Check with the registrar that the domain is active |
| Hybrid routing needs repair | Recipient is on-premises | Give the NDR to the on-premises Exchange admins |
| Duplicate or conflicting recipients | NDR text names "AmbiguousRecipientTransientException" | Look for objects sharing an SMTP or proxy address |
Prove the cause before changing anything
All of these read only.
- Read the NDR's administrator section and keep the full text. Note the code, the recipient domain and, in the proxy-session form, the end point.
- Count how many different recipient domains bounced. One domain points to the destination; all domains point to your side.
- If the NDR contains "Transient Failure during recipients lookup AmbiguousRecipientTransientException", Microsoft says Exchange Online "couldn't uniquely resolve the recipient object": it found several directory objects matching the same recipient and treated the ambiguity as transient.
- For an MX problem at the destination, the destination's admin runs the Outbound SMTP Email test in the Microsoft Remote Connectivity Analyzer.
- Ask the registrar, or look in the registrar's account, whether the domain is active.
Example (illustrative): at contoso.com.au a user's mail to orders@fabrikam.com.au bounces after a day with #550 4.4.7 QUEUE.Expired; message expired ##. Mail to every other external domain delivers. The same bounce arrives for two other fabrikam.com.au recipients, so the scope is one destination domain. The user sends the NDR text and the destination server name to fabrikam.com.au's administrator, who checks the MX record.
Fix
Fix the cause the scope points to.
Your own organisation's mail flow (read only). Microsoft's Solution 1 is to test your organization's ability to send mail by using the Outbound SMTP Email test in the Microsoft Remote Connectivity Analyzer. The test changes nothing in your tenant.
Destination domain. Microsoft lists what its admin can do: "Stop blocking messages from Exchange Online or specifically allow messages from senders in your domain", and check that the MX and other DNS records are set up correctly. You cannot change those records for another organisation. Give them the information Microsoft names: the name of the mail server in the destination domain with the error that server returned, and a copy of the NDR.
Your SPF record. Microsoft's Solution 2 says the SPF record for your domain "might be incomplete, and might not include all email sources for your domain". Microsoft's SPF page says an SPF record has the form v=spf1 <valid mail sources> <enforcement rule>, that only one SPF record is allowed per domain or subdomain, and that "Most Microsoft 365 organizations require include:spf.protection.outlook.com in the SPF TXT record for the domain." Its example for Microsoft 365 email only is:
v=spf1 include:spf.protection.outlook.com -all
Microsoft's example is for a domain whose only mail source is Microsoft 365. A domain with other senders must list those sources too, because -all tells receivers to reject mail from sources that are not listed.
Before you change the record, copy its current text at the registrar into a file kept with the change record.
Risk: the next step edits the SPF TXT record for your whole domain. Every receiving system uses that record. A wrong or duplicate record makes SPF fail for all mail from the domain, and Microsoft says multiple SPF TXT records for one domain or subdomain cause a permerror. Changes can take time to reach receiving systems.
Edit the single existing SPF TXT record at the registrar so it lists every system that sends mail for the domain, and keep it as one record. Microsoft's SPF page says the SPF TXT record for a domain is created "at the domain registrar for the domain" and that no SPF TXT record configuration is available in Microsoft 365.
To undo it, put the saved text back as the domain's one SPF TXT record at the registrar. If no SPF record existed before, the undo is to remove the record you added; the saved copy is then an empty note and nothing is overwritten.
Domain expired. Microsoft's Solution 3 says to verify with your registrar that the domain is active and not expired. Renewal is a commercial step with the registrar.
Hybrid. Microsoft's Solution 4 says that for a recipient on-premises in a hybrid deployment there may be a problem with the hybrid configuration, and that the on-premises Exchange administrators "might need to rerun the Hybrid Configuration Wizard due to changes in their on-premises IP addresses or firewall rules." Give them the NDR. Microsoft's 4.4.7 page gives no steps for the wizard.
Duplicate recipients. Microsoft lists as common causes a mailbox and a mail user sharing one SMTP address, a mailbox and a mail contact with the same proxy address, duplicate mail users or a guest user created during migration, overlapping proxy addresses between on-premises and Exchange Online, the same SMTP address on several recipients, X500 or SIP proxy conflicts, and a "Temporary directory inconsistency", where recent recipient changes are not fully propagated. Microsoft's page gives no commands for finding them. Removing a recipient or changing an address affects mail flow, and Microsoft's page gives no way to reverse it.
Confirm the fix
- Send a new test message to the same recipient. A message put back in the queue is delivered if the receiving server is available, as Microsoft's overview says.
- Ask the recipient to confirm that the test message arrived. Microsoft says the NDR arrives only after 24 hours of failed attempts.
What to watch afterwards
- Other recipients in the same destination domain.
- Any later change to the SPF record, which Microsoft says must remain one record.
- Whether the same recipient bounces with the AmbiguousRecipientTransientException text again.
Read next
Related articles you may want next.
- TroubleshootingExchange Online NDR '451 4.7.500-699 (ASxxx)': IP throttling after the sending server changed its pattern451 4.7.500-699 (ASxxx): Exchange Online is throttling a sending IP that changed its pattern. See when it clears itself and when a connector fixes it.Read article
- TroubleshootingExchange Online "550 5.7.23" bounce: the SPF record, unprovisioned domains and the high-risk delivery poolExchange Online NDR 550 5.7.23: check the SPF record, provision your domains, list on-premises IPs and find the outbound pool by message trace.Read article
- TroubleshootingSPF permerror: too many DNS lookups. Count the limit of 10, then shorten the record safelySPF permerror because the record needs more than 10 DNS lookups. Count the terms that query DNS, find the extra ones and shorten the record safely.Read article
Risks and limits
These commands have not been run or lab-tested.
Microsoft's page names no version range beyond Exchange Online and Microsoft 365. It states a delay of 24 hours, and does not say whether a tenant setting changes it. Only the destination's administrators can fix the destination's records. Registrar and DNS changes affect all mail from the domain.
Sources
- Fix NDR error "550 4.4.7" in Exchange Online — Microsoft Learn, page dated 2026-08-10, accessed 22 November 2026
- Email nondelivery reports and SMTP errors in Exchange Online — Microsoft Learn, page dated 2026-08-24, accessed 22 November 2026
- Set up SPF to identify valid email sources for your custom cloud domains — Microsoft Learn, page dated 2026-07-03, accessed 22 November 2026
This article was originally published on .