How to Fix Email That Will Not Send or Gets Stuck in Outbox

Published 2026-10-16 · Marion Remote Fix

You click Send and the email sits in the Outbox instead of moving to Sent Items. You get a bounce-back notification saying the message could not be delivered. Your email client shows a sending error you do not understand. Email sending failures are common and usually have a straightforward explanation — wrong settings, an attachment that is too large, a temporarily unavailable server, or an authentication problem. Identifying the specific cause gets your email flowing again quickly.

Email stuck in the Outbox

Large attachment

  • The most common reason an email gets stuck in the Outbox is an attachment that exceeds the email provider size limit. Gmail allows 25MB, Outlook.com allows 20MB, and corporate email servers often have their own limits
  • The email client may attempt to send the large message repeatedly, failing each time and keeping it in the Outbox. Each attempt can slow down sending of other messages too
  • Open the stuck message from the Outbox and either remove the attachment or replace it with a smaller file or a cloud storage link (OneDrive, Google Drive). Then try sending again

Offline mode or no internet

  • Desktop email clients like Outlook and Thunderbird have an offline or work offline mode. When enabled, the client composes and queues messages but does not actually send or receive until you go back online
  • In Outlook, check the status bar at the bottom — it shows Connected or Disconnected. Also check the Send/Receive tab for a Work Offline button that may be active
  • In Thunderbird, check the File menu for Work Offline mode
  • Verify your internet connection is working by opening a web browser and loading a page. If the internet is down, email cannot send regardless of client settings

Authentication failure

  • If your email password was recently changed, the email client may still be using the old password. The server rejects the authentication and the message stays in the Outbox
  • If your email provider requires an app-specific password (Gmail with two-factor authentication, for example), using your regular account password in the email client will not work. You need to generate an app password from the email provider account settings
  • Check for any error messages related to authentication or login failure. Update the account password in the email client settings

Bounce-back messages

Understanding bounce-back errors

  • When an email cannot be delivered, the email system sends you a bounce-back or Non-Delivery Report (NDR) containing an error code and message. These codes tell you why the email failed
  • Bounce-backs arrive from a system address like mailer-daemon or postmaster. They are automated messages, not personal responses

Common bounce-back causes

  • Mailbox full (552 or 5.2.2): The recipient mailbox has reached its storage quota and cannot accept new messages. You cannot fix this from your end — the recipient needs to free up space in their mailbox. Try again later or contact the recipient through another method
  • User not found (550 or 5.1.1): The email address does not exist on the destination server. Check the address for typos — a single wrong letter produces this error. Also verify the domain name (the part after the @ symbol) is correct
  • Message rejected by spam filter (550 or 5.7.1): The recipient server rejected the message as spam or because of a policy violation. Your message may contain content that triggers spam filters, your email domain may have a poor reputation, or the recipient server may be particularly strict
  • Server unavailable (421 or 4.7.0): The destination server is temporarily unavailable. This is usually a temporary issue — try sending again in a few hours. The email system may automatically retry for several hours or days before giving up

Outlook-specific sending issues

Outlook profile corruption

  • A corrupted Outlook profile can cause persistent sending failures even when the email settings are correct. Symptoms include emails stuck in the Outbox that cannot be deleted or moved, repeated send/receive errors, and the client hanging when trying to send
  • Try creating a new Outlook profile: open Control Panel, search for Mail, and in the Mail Setup dialog, click Show Profiles. Add a new profile with the same email account settings. Set the new profile as default and restart Outlook
  • If the stuck email transfers to the new profile and sends successfully, the old profile was corrupted. You can delete the old profile after confirming the new one works

Outlook add-in conflicts

  • Third-party Outlook add-ins can interfere with sending. Antivirus email scanning add-ins, CRM integrations, and encryption add-ins sometimes block outgoing messages or cause timeouts
  • Start Outlook in Safe Mode (hold Ctrl while clicking the Outlook icon, or run outlook.exe /safe from the Run dialog). Safe Mode disables all add-ins. If sending works in Safe Mode, an add-in is the cause
  • Disable add-ins one at a time in File, Options, Add-ins to identify which one is causing the problem

SMTP settings

  • If you are using an email client configured with manual server settings, incorrect SMTP (outgoing mail server) settings prevent sending while receiving may still work
  • The SMTP server address, port number, and encryption method must match your email provider requirements. Common settings: Gmail uses smtp.gmail.com on port 587 with TLS (or port 465 with SSL). Outlook.com uses smtp.office365.com on port 587 with TLS
  • The SMTP server requires authentication — your email address and password must be configured in the outgoing server settings, not just the incoming server settings. Some email clients have a separate authentication option for the outgoing server that must be enabled
  • If your ISP blocks port 25 (common to prevent spam), and your email server uses port 25 for SMTP, switch to port 587 with TLS authentication, which most modern email servers support

Sending limits

  • Email providers impose daily sending limits to prevent abuse. Gmail allows 500 messages per day for personal accounts and 2,000 for Google Workspace accounts. Outlook.com has similar limits
  • If you are sending bulk emails (newsletters, announcements, marketing) through a regular email account, you may hit the sending limit. The account is temporarily restricted until the limit resets, usually after 24 hours
  • For bulk sending, use a dedicated email marketing service (Mailchimp, SendGrid, Constant Contact) designed for high-volume sending rather than a personal email account

Webmail vs. desktop client

  • If the desktop email client will not send but the same account works when you log into webmail through a browser, the issue is with the desktop client configuration, not the email account itself
  • Try composing and sending the message through webmail as a workaround while troubleshooting the desktop client
  • If both webmail and the desktop client fail to send, the issue is with the email account or the email server, not your local configuration

ISP and network restrictions

  • Some ISPs (Internet Service Providers) block outgoing email on certain ports to prevent spam from infected computers on their network. This primarily affects custom email server configurations rather than standard provider settings
  • Corporate and school networks may restrict outgoing email to only the organization email server. If you are trying to send from a personal email account on a work or school network, the network firewall may block the connection
  • VPN connections can sometimes interfere with email sending if the VPN routes traffic through a different network path. Try disconnecting the VPN temporarily to test

Email client send/receive errors

  • Error codes like 0x800CCC0E (connection to server failed), 0x800CCC0F (connection dropped), and 0x800CCC78 (sender not verified) are common Outlook error codes with specific meanings
  • Connection errors (0E, 0F) indicate a network problem reaching the email server — check your internet connection, verify the server address and port, and ensure your firewall is not blocking the email client
  • Authentication errors (78, and errors mentioning SMTP AUTH) mean the server is not accepting your credentials. Re-enter your password, check for app password requirements, and verify the authentication settings match your provider requirements

Need help with email sending problems?

If your emails consistently fail to send and you cannot identify the cause, or if you need help reconfiguring your email client with the correct settings, Marion Remote Fix can remotely examine your email configuration, check server connectivity, correct SMTP settings, and resolve authentication issues to get your email working reliably.

← Back to Blog