Overview

When Outlook cannot send email, determine whether the message is stuck only in desktop Outlook or whether the mailbox cannot send from Outlook on the web either. This separates local client problems from mailbox, policy, or Exchange Online problems.

Preserve the error messageDo not repeatedly resend the same message. Capture the exact Outlook error or non-delivery report first.

Why this happens

Sending can fail because Outlook is offline, authentication has expired, a message is stuck in Outbox, mailbox storage is full, the recipient address is invalid, a policy blocks the message, or Exchange Online is experiencing a service issue.

Before you begin

  • Record the recipient, subject, and exact error.
  • Check whether all messages fail or only one.
  • Keep any non-delivery report.
  • Do not change SMTP, DNS, or transport rules during basic troubleshooting.

Click-by-click troubleshooting

Step 1: Test sending from Outlook on the web

Action: Sign in to Outlook on the web in a private browser window and send a short test message to an approved recipient.

Why this matters: This bypasses the desktop Outlook client and tests the mailbox and Exchange Online directly.

What to look for: Confirm whether the web message sends successfully or produces an error.

Expected result: If web sending works, the problem is likely isolated to desktop Outlook.

Step 2: Check Outlook connection mode

Action: In desktop Outlook, review the bottom status bar. Open Send/Receive and confirm Work Offline is not enabled.

Why this matters: Outlook cannot send normally while it is intentionally offline or disconnected.

What to look for: Look for Working Offline, Disconnected, or Trying to connect.

Expected result: Outlook should show a connected state before another send test.

Step 3: Inspect the Outbox

Action: Open Outbox and check for a large message, attachment-heavy message, or item that remains stuck. Do not delete business mail unless you are sure it is safe to recreate.

Why this matters: One malformed or oversized message can block later outbound mail.

What to look for: Look for a single message that never leaves, unusually large attachments, or repeated duplicates.

Expected result: You should know whether the queue is blocked by one specific item.

Step 4: Check mailbox storage

Action: In Outlook on the web, open Settings > General > Storage if available and review quota warnings.

Why this matters: A mailbox at its storage limit can experience send or receive restrictions.

What to look for: Look for full-mailbox warnings or storage near the permitted limit.

Expected result: The mailbox should have sufficient available capacity.

Step 5: Send a plain test message without attachments

Action: Create a new message with a short subject and body and send it to an approved internal recipient.

Why this matters: This separates general sending failure from attachment, recipient, or message-content problems.

What to look for: Compare the test result with the original failed message.

Expected result: A successful plain test points toward the original message or recipient rather than the mailbox generally.

Step 6: Review service health if multiple users cannot send

Action: If authorized, open Microsoft 365 Admin Center > Health > Service health and review Exchange Online incidents.

Why this matters: A broad sending failure can be provider-side rather than a local Outlook problem.

What to look for: Look for Exchange Online mail-flow incidents matching the timeframe.

Expected result: You should be able to identify whether the problem is client-specific, mailbox-specific, or service-wide.

What to look for

  • Web sending succeeds: desktop Outlook problem.
  • Only one message fails: attachment, size, recipient, or content issue.
  • All users fail: Exchange Online or tenant-wide issue.
  • Non-delivery report: preserve the exact diagnostic text.

When to stop

Stop before mail-flow changesDo not change SMTP settings, transport rules, connectors, DNS, or mailbox permissions unless IT directs you.

When to contact IT

Contact J3 Systems Group if Outlook on the web also cannot send, an NDR persists, the mailbox is full, Outlook remains disconnected, or multiple users are affected. Include article code KB-05.003, the error, recipient, and whether web sending succeeds.

Need help with this issue?

J3 Systems Group supports small businesses and nonprofits with Microsoft 365, Google Workspace, cybersecurity, devices, documentation, and day-to-day IT operations.

Contact J3 Systems Group

Authoritative references

Vendor interfaces, licensing, and security guidance can change. Verify current platform behavior against the primary documentation below before making high-impact production changes.

Article KB-05.003 · Review after material vendor, licensing, interface, security, or service changes.