Outlook Emails Stuck in the Outbox: How to Fix Delivery

Outlook emails stuck in the Outbox usually need a restored connection, an offline-mode correction, or a smaller attachment. Before resending anything, establish whether the original message reached the mail server, because repeated attempts can create duplicate deliveries .

For businesses, the safest approach protects unsent work while separating an Outlook app problem from a Microsoft 365 delivery problem. Start with the quick checks below, then follow the instructions for your version of Outlook.

Key Takeaways

• Check connectivity, offline status, attachment size, and whether Outlook is running before changing account settings.
• Keep one working copy of the message, and avoid repeated clicks on Send.
• Use Outlook on the web to help separate an app problem from an account or service problem.

1. Start With Four Quick Checks

Work through these checks before repairing Outlook or removing an account.

1. Test your connection. Open a website, then try your organization's Outlook web mailbox. If appropriate, test an approved mobile hotspot. When several employees fail only on office Wi-Fi, the network needs attention.
2. Look for offline status. In classic Outlook for Windows, inspect the status bar for Working Offline or Disconnected. Select Send/Receive > Work Offline to leave offline mode if it's enabled. Other Outlook apps have different controls.
3. Inspect the attachment. Large files can hold up delivery. Microsoft's general troubleshooting guidance recommends removing attachments larger than 20 MB and trying a smaller file or sharing link. That figure is a troubleshooting threshold, not a universal sending limit.
4. Keep Outlook open. For messages waiting in a local desktop queue, leave Outlook running and the computer awake while it attempts delivery. A closed app can't finish a local send.

Also note whether one message or every message is stuck. A single attachment-heavy email suggests a different problem than an entire office losing email access.

2. Retry Outlook Emails Stuck in the Outbox Safely

Establish Whether the Original Was Submitted

Search Sent Items using the recipient, subject, and approximate sending time. If delivery matters urgently, ask your administrator to examine Exchange Online message trace before you resend.

An Outbox copy doesn't prove that submission failed. A connection can break after the server accepts a message but before Outlook updates its local status. Likewise, a Sent Items entry doesn't prove the recipient read it.

Keep Only One Message Ready to Send

Don't create a replacement in another app while the original remains queued. Once delivery status is clear, move the unsent original to Drafts before editing it, where supported.

Preserve the message text and attachments before deleting anything. If Outlook reports that transmission is underway, stop trying to edit that copy. Use the client-specific recovery steps below, then send the corrected draft once.

3. Clear a Stuck Message in Classic Outlook

Pause Sending and Move the Message

Microsoft's classic Outlook recovery instructions use Work Offline to interrupt the local sending attempt.

Select Send/Receive > Work Offline , then open Outbox. Start with the oldest stuck message and move it to Drafts. This lets you preserve and edit the message without leaving that copy queued for transmission.

If Outlook says it's transmitting the message, close and reopen Outlook, keeping it offline before trying the move again. Don't repeatedly click Send or force-delete the message while Outlook is processing it.

Correct the Draft and Reconnect

Open the draft and remove a problematic attachment. For a large document, use an approved OneDrive or SharePoint sharing link with permissions appropriate for the recipient.

Our guide to sharing large files securely explains when a controlled link is a better choice than an attachment.

Next, select Send/Receive > Work Offline again to reconnect. Send the corrected draft once, then leave Outlook open. For other messages still waiting in the queue, select Send All after confirming that no replacement copies are also queued.

Avoid reopening a message while Outlook is sending it.

4. Use the Right Approach for New Outlook and the Web

New Outlook for Windows

New Outlook doesn't use classic Outlook's Send/Receive ribbon, so those Work Offline instructions don't apply.

First, resolve any visible connection or sign-in warning. Preserve unsent text before restarting the app, then allow it time to reconnect. Don't assume a restart cleared the queue.

If the app offers a way to edit the unsent message or return it to Drafts, use that option after establishing delivery status. Otherwise, involve IT before removing the account or deleting local data. An unsynchronized draft may exist only on that device.

Outlook on the Web

Open the same work account in a browser. Send a separate, small test message with a clearly different subject to an approved internal recipient.

If that succeeds, the desktop app becomes the stronger suspect. However, it doesn't establish whether the original message was delivered.

In the browser, inspect any unsent draft, sending error, sign-in warning, or storage notice. Don't expect classic Outlook's Outbox controls. If both the web mailbox and desktop app fail, investigate the account, network, or Microsoft 365 service before attempting desktop repairs.

5. Recover a Queued Message on Outlook Mobile

On iPhone or Android, confirm that airplane mode is off and Outlook has an active Wi-Fi or cellular connection. Keep the app open while it retries.

If your organization permits it, switch between Wi-Fi and cellular data. A message that sends on one connection but fails on the other points toward a network-specific issue.

Read any account warning, then complete a legitimate sign-in prompt through Outlook. Don't approve unexpected MFA requests.

Before editing a queued message, use the same duplicate-delivery precautions as on desktop. Save unsent text and retain access to attachments before restarting the app.

Avoid uninstalling Outlook or removing the account as an early fix. Those actions can put locally stored, unsynchronized work at risk. If sending works in the web mailbox but mobile remains stuck, give IT the device type, Outlook version, and exact error.

6. Apply Safe Repairs Before Rebuilding Anything

Once you've protected the queued message, restart the affected device and install available Outlook and operating system updates through your organization's normal update process.

For classic Outlook on Windows , Safe Mode can help identify an add-in problem. Press Windows+R , enter outlook.exe /safe , and open Outlook.

If a separate test message sends in Safe Mode, have IT review COM add-ins individually. This test applies to classic Outlook, not new Outlook, the browser, or mobile.

Don't delete Outlook data files, rebuild profiles, or remove accounts without preserving unsent work. Those are later-stage repairs.

Also avoid disabling antivirus, MFA, conditional access, or mail protection to force delivery. A sending problem needs a targeted diagnosis, especially on a business device.

7. Know When an Administrator Should Take Over

Multiple Users, Web Failures, or Uncertain Delivery

Contact your email administrator when several users are affected, web sending also fails, or a business-critical message has uncertain delivery status.

For Microsoft 365, an administrator should open Health > Service health in the Microsoft 365 admin center. Record any relevant incident ID before making configuration changes.

The administrator can also use Mail flow > Message trace in the Exchange admin center to investigate submitted messages. Provide the sender, recipients, subject, approximate time, time zone, and error text. A message still trapped locally might never appear in server-side trace results.

Account Restrictions and Escalation to Microsoft

IT should investigate storage limits, sending restrictions, shared-mailbox Send As permissions, and any rejection message. For mail already submitted, transport rules, connectors, and security policies may explain delivery problems.

A transport-rule change won't repair a disconnected local Outlook queue. If a rule needs changing, preserve its configuration and test a narrow change rather than disabling protections broadly.

Unexpected MFA prompts or unfamiliar mailbox activity also require security investigation.

Escalate to Microsoft support when an unresolved service or account problem persists after local and tenant checks. We help businesses manage Microsoft 365 setup and support, including distinguishing device failures from wider mail-flow issues.

Frequently Asked Questions

What's the Attachment Limit for Outlook?

There isn't one limit that applies to every Outlook account. The mail service, client, organization settings, and recipient system can impose different limits. Microsoft's 20 MB troubleshooting threshold is a practical reason to try an approved sharing link, not a guaranteed maximum.

Does Closing Outlook Stop an Email From Sending?

It can stop a message that still depends on the local desktop app. However, closing Outlook won't cancel mail that the server has already accepted. Don't use closing the app as proof that delivery stopped.

Why Is One Email Stuck While Others Send?

Inspect that message's attachment size and any error attached to it first. Then move the unsent original to Drafts where supported, correct the problem, and retry once. Avoid creating another queued copy.

Restore Delivery Without Losing Control of the Message

The safest fix starts with one preserved message and a clear understanding of its delivery status. Check connectivity first, then use the recovery steps that match your Outlook app.

If the problem reaches multiple users, affects webmail, or leaves delivery uncertain, involve your administrator. A controlled retry is safer than repeated sends or broad account changes.