Why Can’t I Send An Email? | Stop Send Failures

When email won’t send, it feels personal. You hit Send, the spinner runs, then nothing. Or you get a blunt error that tells you zero. The good news: most send issues fall into a small set of causes, and you can narrow them down fast with a clean checklist.

This walk-through is built for normal inboxes (Gmail, Outlook, iCloud, workplace accounts) and for custom domains (you@yourdomain.com). You’ll start with the fastest checks, then move into the fixes that handle the tricky cases: authentication loops, blocked ports, oversized attachments, mis-set outgoing servers, and provider security locks.

Start With A 3-Minute Triage

Before you change settings, figure out what kind of failure you have. That choice saves time.

Step 1: Look At Where The Message Is Stuck

• Stuck in Outbox: The app can’t hand it off to the outgoing server.
• Disappears but never arrives: It left your device, then got rejected or filtered later.
• Bounces back with an error: The receiving side rejected it, or your provider blocked it.

Step 2: Send A Tiny Test Message

Create a new email with a short subject and one line in the body. No attachments. Send it to an address you can check right away (like a second inbox you own). If the tiny message sends, your issue is often size-related or tied to one specific draft.

Step 3: Check If It’s One Device Or All Devices

• Only one device fails: App settings, cached credentials, or network rules on that device.
• All devices fail: Account lock, password change, provider outage, or a billing/storage limit.

Why Can’t I Send An Email? Common Causes And Fixes

Most “can’t send” problems come down to the outgoing side of email, not the inbox. Reading uses IMAP or Exchange sync. Sending uses SMTP submission, which is stricter about logins, ports, and security.

Fix 1: Clear A Stuck Outbox

A single bad draft can block everything behind it. This happens a lot with big attachments, flaky Wi-Fi, or a message composed while offline.

1. Open the Outbox (or “Sending…” folder).
2. Open the oldest stuck message first.
3. Try one of these quick moves:
   • Remove attachments, save, then send.
   • Copy the text into a brand-new email and send the new one.
   • Delete the stuck message, then retry sending the next message.

Fix 2: Confirm You’re Online On The Same Network You’re Sending From

This sounds obvious, yet it’s sneaky: a device can show “connected” while the network blocks mail traffic. Public Wi-Fi, captive portals, and some office networks do this.

• Open a web page you don’t usually have cached.
• If you’re on public Wi-Fi, open your browser and complete any sign-in splash page.
• Switch to mobile data or another Wi-Fi network and retry sending.
• If sending works on mobile data, your Wi-Fi network is the constraint.

Fix 3: Re-Sign In After A Password Or Security Change

Email apps don’t always prompt cleanly after a password update or a security alert. Instead, they fail on send with a generic message.

• Log in to your email provider on the web and confirm your password works.
• If you use two-step verification, confirm you can complete it on the provider site.
• Back on your device, sign out of the account in the mail app, then sign in again.

Fix 4: Check Mailbox Storage And Attachment Limits

Some providers allow reading mail even when you’re at storage limits, then block sending until space is freed. Large attachments can also hit per-message caps, which vary by provider and account type.

• Try sending the same message without attachments.
• Upload the file to cloud storage and send a link instead.
• Free space by deleting large messages with attachments, then empty Trash.

Fix 5: Watch For “Sent” That Isn’t Really Sent

Some apps show a message in Sent before the server confirms final delivery. If recipients never get it, look for a bounce message later, or check the provider’s “Sent” folder on the web to confirm it truly left your account.

Fix App-Level Problems On Windows, Mac, iPhone, And Android

If your account sends fine on the provider website but fails inside an app, focus on the app layer: updates, stored credentials, and account tokens.

Update The Mail App And Restart

It’s plain, but it works. Restarting clears hung send processes and forces a clean reconnect. Updating fixes broken auth flows after provider security changes.

• Update the mail app (Outlook, Apple Mail, Gmail app).
• Restart the device.
• Try sending the tiny test message again.

Remove The Account And Add It Back

This is the fastest reset for weird send behavior after a password change, a migration, or a corrupted local profile. It refreshes server settings and tokens.

• On iPhone/iPad, Apple’s steps for Mail account reset are laid out in “If you can’t send email on your iPhone or iPad”.
• On Outlook.com accounts, Microsoft’s checklist for send/receive issues is in “Can’t send or receive email in Outlook.com”.

Check For A Stuck Draft With A Bad Character Or Broken Attachment

Some drafts break in ways that aren’t obvious: an attachment placeholder that points nowhere, a pasted table that the app can’t encode, or a copied email thread that’s huge. If one message fails, rebuild it from scratch.

1. Create a new email.
2. Type the text fresh, or paste into a plain-text editor first, then copy back.
3. Add attachments one at a time to see which one triggers the failure.

Check SMTP Settings If You Use A Custom Domain Or ISP Email

If your email address is tied to a domain host, an ISP mailbox, or a business server, sending depends on outgoing server details. Receiving can still work while sending fails.

Know The Three SMTP Details That Matter

• SMTP server name: Often looks like smtp.yourdomain.com or mail.yourhost.com.
• Port: Common submission ports are 587 (STARTTLS) and 465 (SSL/TLS). Port 25 is mainly server-to-server and is often blocked on consumer networks.
• Authentication: “SMTP auth” must be on, using your full email address as the username in many systems.

Spot The “Receive Works, Send Fails” Pattern

This pattern usually means the outgoing server is wrong, the port is blocked, or the app is trying to send without authentication. A quick test is to try the same account on a different network. If it sends on mobile data but not on home Wi-Fi, the network is the bottleneck. If it never sends anywhere, settings are the bottleneck.

Check TLS And Certificate Warnings

If your mail app shows a certificate warning, don’t click past it blindly. A mis-issued cert or a wrong server name can break secure sending. Match the server name to what your email host documents. If the host changed your mail server, update your account settings to match the new host name.

Fix Provider Blocks, Security Locks, And Spam Rejections

Sometimes your setup is fine, yet sends still fail because the provider is protecting the account or rejecting the message content.

Check For Account Security Holds

Providers may pause sending after suspicious sign-ins, sudden bursts of outbound mail, or malware flags. If every device fails, sign in on the provider website and look for security prompts, alerts, or a request to confirm recovery info.

Reduce Links And Formatting In The Message

If a message bounces with “rejected,” “blocked,” or “content not accepted,” simplify it:

• Remove extra links.
• Send plain text.
• Drop big images and long signatures.
• Try a clean subject line with normal words.

Watch For Blacklist And Reputation Issues On Custom Domains

If you send from a custom domain and messages get rejected by larger providers, you may have missing DNS records or a reputation problem. This often shows up as bounces that mention SPF, DKIM, or DMARC.

• Confirm SPF and DKIM are set for your domain in DNS.
• Confirm your sending server matches what SPF allows.
• If you use a third-party sender (newsletter tool, CRM), use their documented DNS values.

Fix Network And Firewall Blocks That Stop Sending

Mail sending can fail when networks block outbound connections used for SMTP submission. This is common on locked-down office networks, hotels, and some home ISP setups.

Try Another Network

Switch to mobile data or a different Wi-Fi network, then retry the tiny test message. If that works, your original network is blocking mail traffic or doing deep inspection that the mail app can’t handle.

Check VPN And Security Software

Some VPN profiles and endpoint security tools intercept secure connections. If sending breaks right after enabling a VPN or a new security app, turn it off and test once. If it’s the cause, add your mail app as an allowed app, or use a VPN profile designed for mail traffic in your workplace.

Edge Cases That Waste Time If You Miss Them

These cases are less common, yet they explain the weirdest “it worked yesterday” failures.

Wrong From Address Or Alias

If you’re sending from an alias, shared mailbox, or “Send As,” the server may block it unless you have permission. Test by sending from the main address tied to the login.

Time And Date Are Off On The Device

Secure connections depend on time. If the device clock is off by a lot, TLS handshakes can fail and mail won’t send. Set time to automatic, restart, then test again.

Server Outage Or Maintenance

If mail won’t send on all devices and webmail also fails, it may be a provider outage. In that case, local changes won’t help. Check your provider’s status page if they offer one, then retry later.

A Clean Send Checklist You Can Reuse

When you want the fastest path from “won’t send” to “fixed,” run this in order:

1. Send a tiny test message with no attachment.
2. Clear the Outbox and delete the oldest stuck draft.
3. Switch networks (Wi-Fi to mobile data) and test again.
4. Sign in on the provider website to confirm the account is healthy.
5. Re-sign in inside the app, or remove and re-add the account.
6. If using a custom domain, verify SMTP server, port, and SMTP auth.
7. If bounces mention SPF/DKIM/DMARC, fix DNS for your domain sender.

If you follow that list, you’ll solve most send failures without guesswork. When it still won’t send, the error text from the bounce message is your next clue. Copy it into a note, then match it to the categories above: auth, port, size, content, or domain policy. That’s the shortest route to a stable fix.

Send us your feedbackTell us what you thought about this post

Name * Email *

Your comment *

Quick check — what is …? *

Send feedback