Skip to content
Microsoft (Outlook.com and Microsoft 365) · temporary error

4.4.7: message expired in the queue

Exchange Online kept retrying a message for a day, the receiving server never accepted it, and the message expired.

Microsoft
Provider
Temporary (4xx)
Class
Sources checked
Author

At a glance

Code
4.4.7
Temporary or permanent
TemporaryThe sending server keeps the message and tries again later.
Who has to act
Either side, depending on the cause. Start with the checks below that are yours.
What the server says
4.4.7 QUEUE.Expired; message expired

What it means

Exchange Online returns this after it has tried to deliver a message for 24 hours without success. Each attempt met a temporary refusal, a timeout or no answer at all, so the service kept the message queued until it expired, then sent this report. Microsoft writes it as 550 4.4.7: the 4.x.x code records that the underlying failures were temporary, while the report itself is final and the message will not be retried. Most often the destination is at fault: its server is down, its MX record is wrong, or it refuses Microsoft servers. Sometimes the cause sits on the sending side, in SPF, an expired domain or a hybrid connector, or in a directory conflict reported as AmbiguousRecipientTransientException.

Common causes

  • The destination mail server is offline, unreachable or refusing connections from Exchange Online.
  • The destination domain has a missing or wrong MX record.
  • A network problem made every delivery attempt time out.
  • Two directory objects share the recipient address, so Exchange Online cannot resolve the recipient (AmbiguousRecipientTransientException).
  • A hybrid connector to the on-premises organization no longer matches its IP addresses or firewall rules.

How to fix it

  1. 01Check whether only one destination domain is affected; if so, tell the recipient by another channel and pass on the remote server name and error from the report.
  2. 02The destination's admin should check the domain's MX and DNS records, for example with the Outbound SMTP Email test in Microsoft Remote Connectivity Analyzer.
  3. 03If other domains are affected too, test your own tenant with the same analyzer and check that your SPF record lists every source of your mail.
  4. 04Confirm with your registrar that your domain has not expired.
  5. 05In a hybrid setup, give the report to the on-premises admins, who may need to rerun the Hybrid Configuration Wizard.

Sources

What this page rests on, checked on 20 Oct 2026. The explanation is ours; the reply text is the server's.

  1. 5.4.300Message expired and the report could not be returned.The message was not delivered in time because the destination did not respond or an error occurred, and the report could not reach the sender.MicrosoftPermanent
  2. 4.4.316Destination server refused the connection.Exchange Online is trying to deliver outside Microsoft 365, but every connection to the receiving server is being refused.MicrosoftTemporary
  3. 4.4.7Delivery time expired.The message stayed undelivered for too long, usually because every retry failed, so the server gave up on it or warned that it is delayed.StandardTemporary

Further reading

All 111 Microsoft codesEvery code in the wikiPaste your own bounce

Beat · paid monitoring

A heartbeat for your email.

Beat runs every check on this site on a schedule: 41 checks, 33 blacklists and real inbox placement. The moment something breaks, it tells you what broke, why it matters, and the exact fix.

example.comWatching
  • SPFpass
  • DKIMpass
  • DMARCp=none
  • Blacklists0 of 33

Illustrative. Your domain, every few hours.

Also from us:Pulse: your own sending infrastructureConsulting: $65/hr, no retainer