Recommended Free Tools
That Outlook message—Message cannot be sent right now—isn’t one single problem. It’s a generic symptom that typically points to a connectivity issue, a stuck send queue (Outbox), a broken add-in, or a server-side policy that rejects the send.
This guide walks you through the fixes that most often resolve it, starting with quick checks and moving toward deeper repairs. You’ll get working steps for Outlook for Windows (classic and New Outlook), Outlook on the web, and mobile (iPhone/iPad and Android).
As an Amazon Associate I earn from qualifying purchases.
If you want the fastest resolution, read the “Before You Change Anything” section first, then jump to the client you’re using.
What the Outlook Error Means
When Outlook can’t send a message, it usually fails before (or during) SMTP submission. The message may sit in Outbox, Drafts, or Sent Items without actually reaching the recipient.
#1 Best Overall
Depending on your setup (Exchange/Microsoft 365 vs IMAP/POP), the underlying cause could be local (Outlook profile, OST cache, add-ins) or remote (mail flow rules, authentication, mailbox limits).
Before You Change Anything (Quick Checks That Actually Help)
Start here—these checks often determine the right fix in minutes.
- Check internet connectivity: open any website and verify it loads. If you’re on a VPN, try temporarily turning it off.
- Look for the message state: does it sit in Outbox or bounce back instantly? If it lands in Outbox, Outlook is queueing but not transmitting.
- Try sending a tiny test email: no attachments, short subject, one recipient. If that works, the issue is likely attachment-related or triggered by a rule/add-in.
- Confirm the correct mailbox: if you have multiple accounts, send from the account that owns the error (verify From address).
If the tiny email still fails, go straight to the client-specific steps below.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallCommon Causes Behind Message Cannot Be Sent Right Now
Most cases cluster into a few buckets. Use this list to predict where the problem lives.
- Offline or interrupted connection (Outlook set to work offline, network drops, proxy/VPN interference).
- Stuck Outbox due to a corrupted send attempt or queued message.
- Add-in conflicts (security/CRM/document tools are frequent culprits).
- Corrupted mailbox cache (OST) or a damaged Outlook profile.
- Server-side restrictions (transport rules, DLP policies, blocked recipients/attachment types).
- Mailbox limits (quota) preventing new messages from being sent.
- Authentication failures (OAuth/modern auth token issues; SMTP relay problems).
Fixes for Outlook on Windows (Classic Outlook)
The classic Outlook client is still the most common setup in enterprises and personal machines. Use these steps in order.
1) Confirm you’re online and not stuck in Offline Mode
Classic Outlook can silently fall into Offline Mode, which causes sends to fail or queue endlessly.
- Open Outlook.
- Go to Send/Receive.
- Click Work Offline to make sure it’s not enabled (the button should not be active).
- Click Send/Receive All Folders.
Try sending your test email again.
2) Send immediately and clear stuck items from Outbox
If messages are stuck, clear the queue so Outlook can rebuild a clean send attempt.
Free tools Windows power users keep installed
One-click scans. No signup required.
- In Outlook, go to Mail.
- Open the Outbox folder (you can search for “Outbox” in the folder list).
- If you see messages waiting, right-click each one and choose Delete (or Move > Drafts if you need to resend).
- Go back to Send/Receive and click Send/Receive All Folders.
Then send a new test message.
3) Disable add-ins (especially if only some messages fail)
Add-ins can block sends, rewrite recipients, or fail during message creation. If only certain emails fail (e.g., with signatures, templates, CRM fields, or attachments), start here.
- In Outlook, go to File > Options.
- Select Add-ins.
- At the bottom, next to Manage, choose COM Add-ins and click Go….
- Uncheck all non-Microsoft add-ins (leave Microsoft items alone).
- Click OK and restart Outlook.
- Try sending the test email again.
If it works, re-enable add-ins one at a time until you find the offender.
4) Rebuild the mailbox cache (OST) when Outlook is flaky
A corrupt OST can prevent proper submission. Rebuilding fixes this in many “it works sometimes” cases.
Warning: Close Outlook first. The OST will be recreated.
- Close Outlook.
- Open Control Panel > Mail (32-bit if present) > Show Profiles.
- Select your profile and click Properties.
- Choose Data Files.
- Select the relevant OST, then click Open File Location (or note the path).
- Back in Outlook’s Data Files window, note the OST filename and close all dialogs.
- Delete or rename the OST file (Outlook will recreate it on next launch).
- Reopen Outlook and test sending.
If you’re on an Exchange account, OST rebuild is typically safe for local cache issues.
5) Repair the Office/Outlook install
If Outlook components are damaged, repair often resolves sending failures that persist even after cache and add-in changes.
- Close Outlook.
- Open Settings > Apps > Installed apps.
- Find your Microsoft 365/Office product.
- Click Modify.
- Choose Quick Repair first, then test.
- If not fixed, run Online Repair.
Online Repair can take longer, but it’s more thorough.
Fixes for New Outlook for Windows
New Outlook behaves differently from classic Outlook, and the menus aren’t identical. Still, you can isolate the cause quickly with restarts, add-in checks, and basic send tests.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →1) Restart and re-sync your mailbox
A simple restart can clear a stuck send state.
- Fully quit New Outlook (not just the window).
- Reopen it and wait for the inbox to finish syncing.
- Send a tiny test email with no attachments.
If the send works after re-sync, the issue was likely transient network/auth.
2) Disable add-ins and extensions
Even in the new client, integrations can interfere with compose/send.
- Open New Outlook.
- Go to Settings (gear icon).
- Find Extensions or Add-ins (wording can vary by build).
- Disable all third-party items.
- Restart the app and retest sending.
3) Test a simple email to isolate server vs. client issues
Try sending to an external address (e.g., Gmail/Outlook.com). If it fails only for internal recipients, that points to address/transport rules rather than your Outlook install.
Rank #3
- The Microsoft Office 365 Bible: The Most Updated and Complete Guide to Excel, Word, PowerPoint, Outlook, OneNote, OneDrive, Teams, Access, and Publisher from Beginners to Advanced
- ABIS BOOK
Fixes for Outlook on the Web (OWA)
If OWA can send but desktop cannot, your problem is almost certainly local (classic Outlook cache/profile/add-in). If OWA also fails, the issue is likely server-side or policy-related.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →1) Check mailbox state and resend
- Sign into Outlook on the web.
- Look for an Outbox or pending items view (availability depends on tenant).
- Resend after removing the attachment or simplifying the message.
If the simplified email succeeds, the original failure was probably attachment or rule-triggered.
2) Remove rules and verify permissions
Transport rules and client-side rules can block sends or redirect messages.
- In OWA, open Settings > MailRules.
- Temporarily disable rules related to forwarding, redirecting, or condition-based actions.
- Try sending again.
If you’re in a corporate environment, you may also need admin confirmation for DLP policies.
3) Clear browser cache and try a private window
If OWA fails only in one browser or one profile, a cached session or extension can break sending.
- Open a private/incognito browser window.
- Sign in to OWA and try the send.
- If that works, clear cache/cookies for Microsoft 365/Outlook domain and disable browser extensions.
Fixes for Outlook on iPhone and iPad (iOS)
Mobile sends can fail due to background sync restrictions, stale authentication tokens, or app configuration issues. Apply the steps below in order.
1) Verify account sync settings
- Open Settings on your iPhone/iPad.
- Go to Mail > Accounts > select your Outlook/Microsoft account.
- Confirm Mail is enabled and sync is allowed.
- On the Outlook app, open it and check account settings for sync behavior.
Then try sending a tiny message.
2) Update iOS and the Outlook app
- Update iOS via Settings > General > Software Update.
- Update the Outlook app in the App Store.
App versions matter because send/auth flows are continuously adjusted.
3) Remove and re-add the account (last resort)
This clears stale tokens and config inconsistencies.
- On iPhone/iPad, go to Settings > Mail > Accounts.
- Select the Outlook/Microsoft account.
- Tap Delete Account.
- Re-add the account inside the Outlook app (preferred) or Mail settings.
- Test sending a simple email.
Fixes for Outlook on Android
Android clients commonly fail due to background restrictions, outdated app builds, or authentication token refresh issues.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
1) Confirm connectivity and background sync
- Toggle Wi-Fi and mobile data to confirm the network is stable.
- Check battery optimization for the Outlook app: Settings > Apps > Outlook > Battery > set to Unrestricted or Not restricted.
- Open Outlook and let it fully sync.
- Try sending a tiny email with no attachments.
2) Update Outlook and Android system components
- Update the Outlook app from Google Play.
- Update Android OS via Settings > System > System update.
3) Remove and re-add the account (last resort)
- In Outlook, open Settings (profile icon) > select the account.
- Choose Remove account.
- Add it again and sign in.
- Send a test message.
When the Error Is Caused by Your Mailbox or Server
If every client fails (desktop, New Outlook, and OWA), your tenant or mailbox likely rejects outgoing messages. Here are the common server-side triggers.
Message size, attachments, and blocked file types
Many organizations enforce message size limits and block executable or risky file types.
- Test by removing attachments.
- If you must send files, try compressing them into a .zip archive (if allowed) or use OneDrive/Share links instead of direct attachments.
- If the failure happens only with one recipient, check whether that recipient is blocked or requires special addressing.
Mailbox quota and storage limits
If your mailbox is near quota, sends can fail. Ask your admin to check quota (Exchange/Microsoft 365).
- In OWA, check mailbox usage in Settings/Subscription (where available).
- Or use your admin portal to verify quota and warning thresholds.
Authentication issues (SMTP or OAuth)
When modern auth tokens expire or SMTP submission settings break, Outlook shows generic send errors.
Signs include: sends fail suddenly across devices, or OWA fails too after a sign-in change. In this case, re-authenticating (remove/re-add account) often clears the token problem.
Corporate policies, transport rules, and DLP
Transport rules can prevent sends based on content, subject patterns, external recipient restrictions, or protected document handling.
If you’re in an organization, the most reliable path is to ask your admin to check message trace / audit logs for the recipient and timestamp.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.What to Try When the Main Fixes Fail
When the obvious steps don’t work, you need isolation and diagnostics. Use these in sequence.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Scan for outdated or missing drivers - takes under a minute3Repair Windows errors before they cause bigger problemsTest from a different device and a different client
- Try sending the same simple email from your phone and from your web browser.
- If web works but desktop fails, you’re dealing with Outlook-specific cache/profile/add-ins.
- If all clients fail, focus on mailbox/tenant policies or authentication.
Use a fresh Outlook profile
A corrupt Outlook profile can cause send failures even with a healthy network.
- Close Outlook.
- Open Control Panel > Mail.
- Click Show Profiles.
- Create a new profile.
- Add the same account.
- Set it as Always use this profile and test sending.
Safe Mode diagnostics
Safe Mode loads Outlook with minimal add-ins, which helps identify conflicts.
- Press Win + R.
- Type:
outlook.exe /safeand press Enter. - Try sending your test email.
If it works in Safe Mode, you can confirm an add-in conflict and remove/re-enable add-ins accordingly.
Check event logs and sync health (advanced)
If you have access to Windows logs, check for Outlook/Office related errors around the timestamp of the failed send. Also validate Microsoft 365 service health in your tenant admin center if you suspect broader outages.
Common Mistakes That Keep the Problem Coming Back
- Only changing one thing: you might disable an add-in but keep the same stuck Outbox message queued.
- Ignoring Outbox: deleting the problematic draft without clearing Outbox can leave Outlook in a failed send loop.
- Testing with complex emails only: if you don’t test a minimal email, you won’t know whether attachments, rules, or policies are involved.
- Overlooking account selection: sending from the wrong account can trigger a different SMTP/OAuth setup and fail.
Comparison: Which Fix Works Best for Which Scenario
| Scenario | Most likely cause | Best first fix |
|---|---|---|
| Classic Outlook fails, OWA works | Local Outlook issue (add-in, OST, profile) | Disable COM add-ins, then clear Outbox |
| New Outlook fails, classic works | New Outlook extension issue or stale sync | Restart, then disable extensions and retest |
| OWA also fails | Server-side restriction or authentication | Simplify message; check rules/policies; ask admin for trace |
| Only emails with attachments fail | Attachment type/size policy | Remove attachment and test; then switch to safe sharing |
| Fails suddenly after password/MFA changes | Stale tokens or re-auth needed | Remove and re-add account |
Bottom Line
“Message cannot be sent right now” is usually fixable by clearing the local send queue, removing add-in conflicts, and rebuilding Outlook’s cache/profile when needed. If Outlook on the web fails too, focus on server-side policies, mailbox limits, and authentication.
Use the quick test email strategy to isolate whether the problem is attachments/rules vs. a deeper client or tenant issue—then apply the matching fix for your platform.
FAQs
Q: Why does Outlook show Message cannot be sent right now even though my internet works?
Outlook may be queueing the message due to Offline Mode, an add-in blocking submission, a stuck Outbox, or an authentication failure for SMTP/OAuth. Your network test alone doesn’t confirm Outlook’s send pipeline is healthy.
Q: What if deleting messages from Outbox doesn’t help?
That points to a persistent profile/OST/cache problem or an add-in conflict. Try disabling COM add-ins, then rebuild the OST or create a fresh Outlook profile.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchPC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Q: Will Office Online/Word or attachments from iCloud fix this?
Using OneDrive/iCloud links can help if the issue is attachment size or blocked file types, but it won’t fix client-side send queue problems.
Q: How do I know if it’s server-side?
If OWA also can’t send the same minimal email (no attachments, one recipient), it’s almost always tenant-side (policies/DLP, quotas, or authentication) and should be verified via message trace by your admin.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
