A message that sits in the Outbox is not a message that failed. It is a message the client accepted and has not handed off yet, and there are only a handful of documented reasons that handoff does not happen. Work through them in order of cost, and do the first one before touching anything else: stop the retry loop. As long as the client keeps trying to transmit the item, the item stays locked, and attempts to delete or edit it either do nothing or hang the app.
The rest of this depends on something most guides skip. Microsoft now ships two different Windows mail clients under the same name, and the menus that fix this problem exist in only one of them.
Establish which Outlook is running before following any menu path
Classic Outlook for Windows and new Outlook for Windows are separate applications with separate interfaces. Microsoft's own article on messages stuck in the Outbox carries an "applies to" list of Outlook for Microsoft 365, Outlook 2024, Outlook 2021, Outlook 2019, and Outlook 2016 — all classic builds. The steps in it reference a ribbon tab that new Outlook does not have.
The fastest test is the ribbon itself. If a Send / Receive tab sits along the top of the main mail window, classic Outlook is running. If there is no Send / Receive tab at all and the ribbon is a single simplified strip, new Outlook is running. Every procedure below is labelled for one or the other.
Clearing the queue in classic Outlook
Microsoft's published procedure names one cause up front: "the most likely cause is a large attachment." The steps are ordered so that the retry loop stops before the message is touched.
- On the Send / Receive tab, choose Work Offline. The status bar changes to read Working Offline. Nothing further is transmitted while this is set.
- Open the Outbox folder from the navigation pane.
- Either select the message and press Delete, or drag it into Drafts, open it, select the attachment, and press Delete to strip the attachment while keeping the text.
- If Outlook will not respond at all, press Ctrl+Alt+Delete, open Task Manager, find outlook.exe on the Processes tab, and end the process. Restart Outlook and repeat steps 2 and 3.
- Choose Send / Receive > Work Offline a second time to return to the connected state. Microsoft's guidance is explicit that this is a toggle: "if the status shows Working Offline, repeat the action until the status changes to connected."
The reverse case matters just as much. A message can land in the Outbox simply because Work Offline was already on when Send was pressed — Microsoft describes this as messages getting stuck "when you click Send but you're not connected." Check whether the Work Offline button is highlighted. Turn it off, then use Send All to push the queue.
What is different in new Outlook
New Outlook has an Outbox folder — Microsoft's own feature comparison table lists the Outbox as available in both clients. What it does not have is a Work Offline command. Offline behaviour is a setting rather than a toggle:
- Settings > General > Offline, then the toggle Enable offline email, calendar, and people, then Save.
- Under the same section, Folders to save chooses between Default, Default and favorites, and Default, favorites, and recently used.
- Days of email to save offers four values: 7, 30, 90, or 180.
The same comparison table rates offline support as Available in classic Outlook and Partially available in new Outlook. That difference is worth taking at face value when a message will not leave a new Outlook Outbox — the offline layer behaves differently, and Microsoft has not published a new Outlook equivalent of the five-step Outbox procedure above.
The size caps, and why more than one applies
Attachment limits are not a single number. Several separate caps sit in series, and the smallest one that applies is the one that stops the message. Two of them are enforced on the PC before anything reaches a server.
In classic Outlook, the client-side default is 20 MB (20480 KB) for internet email accounts — POP3, IMAP, HTTP — and 10 MB (10240 KB) for Microsoft Exchange Server accounts. Both are governed by a MaximumAttachmentSize DWORD under HKEY_CURRENT_USER\Software\Microsoft\Office\<x.0>\Outlook\Preferences, expressed in KB, where 0 means no client-side limit and <x.0> is the Office version (16.0 covers Office 2016 through Microsoft 365).
Server-side, an Exchange Online mailbox defaults to 35 MB for sending and 36 MB for receiving, and an administrator may set any value between 1 MB and 150 MB. Outlook.com applies 25 MB to a file attachment, with OneDrive links allowed up to 2 GB.
The cap that catches people out is the last one. Messages routed outside Microsoft datacenters are subject to an additional 33% translation encoding increase, which is why the practical ceiling for Outlook on the web is quoted as 112 MB rather than 150 MB. A file that looks comfortably under a limit in File Explorer can exceed it once encoded.
One more ceiling is easy to trip during a bulk send: Exchange Online allows a maximum of 250 file attachments per message, and treats 250 as the multipart limit as well.
A held message and a stuck message look identical in the folder list
Classic Outlook can be told to hold an individual message deliberately. Microsoft describes the behaviour plainly: you can "delay the delivery of an individual message by having it held in the Outbox for a specified time after you select Send." Nothing in the Outbox view distinguishes that from a failure.
To check, open the message and look at Options > More Options > Delay Delivery. That opens the Properties dialog "with the Do not deliver before check box selected." Clear the box to release the message immediately. Microsoft also notes that the setting is per-message — "you must choose Delay Delivery for each message that you want to delay" — so a whole Outbox full of held mail almost always means a rule is doing it, since "everyone can use rules to delay the delivery of all messages by holding them in the Outbox."
New Outlook works the opposite way
New Outlook and Outlook on the web use Schedule send, reached from the dropdown next to Send. Crucially, a scheduled message stays in the Drafts folder, not the Outbox. To release it, open Drafts, open the message, select Cancel send, then Send. Microsoft also states that Schedule send "is unavailable for IMAP or POP accounts."
Microsoft's feature comparison reflects the split directly: Schedule send is listed as Not supported in classic Outlook and Available in new Outlook, while the delay send rule is Available in classic and Partially available in new. So a message waiting in a new Outlook Outbox is not a scheduled message — scheduled items are somewhere else entirely.
Two classic settings that hold mail without any error
If the Outbox empties the moment a manual send/receive is triggered, the transport is fine and a setting is responsible.
The first is Send immediately when connected, at File > Options > Advanced > Send and receive. Microsoft's troubleshooting article identifies the disabled state of exactly this option as the cause of mail that "stays in Outbox until manually send or receive," backed by a Send Mail Immediately DWORD set to 0 under HKEY_CURRENT_USER\Software\Microsoft\Office\<x.0>\Outlook\Options\Mail. If the checkbox is greyed out, it is being enforced by group policy and an administrator has to remove the policy.
The second is the send/receive schedule. Send / Receive > Send/Receive Groups > Define Send/Receive Groups exposes the Schedule an automatic send/receive every n minutes option and a per-account Include the selected account in the group checkbox. An account excluded from the group, or a long interval, produces exactly the symptom under discussion. F9 forces a manual send and receive, which is the quickest way to confirm this is what is happening.
Recipient and rate limits usually bounce rather than stall
Quota problems behave differently from the cases above: the message normally leaves the Outbox and comes back as a non-delivery report. Recognising the code saves a long detour through client settings.
| Limit | Exchange Online (work or school) | Outlook.com (personal) |
| Recipients in one message | Customizable up to 1,000 across To, Cc, and Bcc | 500 |
| Recipients per 24 hours | 10,000 | 5,000 for Microsoft 365 subscribers |
| Non-relationship recipients per day | Not published as a separate figure | 1,000 for Microsoft 365 subscribers |
| Message rate | 30 messages per minute | Not published |
| Meeting invitations | 5,000 recipients maximum | Not published |
Two figures deserve a caveat. Microsoft states that Outlook.com limits "may vary based on usage history and will be lower for non-subscribers," and that a newly created Outlook.com account carries "a low sending quota" as "a temporary restriction which is upgraded to the maximum limit as soon as you establish credibility." Microsoft does not publish what the reduced starting values are.
The relevant Exchange Online bounce codes are worth reading literally rather than guessing at:
5.1.90— "Your message can't be sent because you've reached your daily limit for message recipients." The sender exceeded the recipient rate limit.5.2.2— "Submission quota exceeded." The sender exceeded the recipient rate limit or the message rate limit.5.2.121— the sender exceeded the number of messages allowed per hour to one specific recipient.5.2.122— the recipient exceeded the number of messages they can receive per hour from all senders. This one is not the sender's fault and no client-side change fixes it.
Once a recipient rate limit is hit, Microsoft's description is that "messages can't be sent from the mailbox until the number of recipients that were sent messages in the past 24 hours drops below the limit." Waiting is the fix; retrying is not.
Points where the documentation stops
Several things commonly asserted about this symptom are not published by Microsoft, and are left out here rather than guessed at.
- Why a specific item locks. Microsoft documents the workaround — go offline, then move or delete — but does not publish the internal reason a message in transmission cannot be modified. The workaround is documented; the mechanism is not.
- A new Outlook equivalent of the Outbox procedure. The stuck-Outbox article applies to classic builds only. New Outlook has an Outbox folder, but Microsoft has not published a matching step list for it.
- The Undo send interval in new Outlook. Microsoft's message recall article directs personal-account users to "the 'Undo Send' delay feature in new Outlook for Windows or Outlook.com" instead of recall, but that article does not state the delay length. A brief hold caused by that feature is real; the exact number of seconds is not documented on that page.
- Reduced quotas for new accounts. Confirmed to exist, value not published.
When This Doesn't Apply
This frame assumes the message is genuinely queued on the client. Several situations look the same and are not.
- Outlook on the web with no desktop client involved. Browser-based Outlook has no local Outbox that survives a session and no Work Offline toggle. If a message will not send there, the problem is server-side or size-related, and the client procedures above have nothing to act on.
- A scheduled message in new Outlook. It is in Drafts, not the Outbox. Emptying the Outbox will not find it, and nothing is wrong.
- Message recall being confused with a send failure. Recall requires that "both you and the recipient have a Microsoft 365 work or school email account in the same organization, and the recipient hasn't opened the message yet." Personal accounts — Gmail, Hotmail, Outlook.com — cannot use recall at all, so a recall attempt is never the reason mail is sitting in an Outbox.
- Administrator-set limits below the defaults. An Exchange Online tenant may be configured anywhere from 1 MB to 150 MB. A 20 MB attachment that works from one work account and fails from another is a policy difference, not a fault, and only an administrator can confirm the value in force.
- A greyed-out setting. If Send immediately when connected cannot be changed, group policy owns it. No local fix exists; the request goes to whoever manages the policy.
- Genuine service incidents. None of the above distinguishes a client problem from an outage. Check the service health dashboard for a work or school account before spending time on client settings.
Worked in the order shown — delay first, offline second, size third, send-on-connect fourth, schedule and quota last — most cases resolve at step two or three, and the ones that do not will produce a bounce code specific enough to act on.
Comments
Post a Comment