An outlook send receive error is one of the most frustrating problems in the desktop app: your emails sit stuck in the Outbox, new messages refuse to arrive, and Outlook either shows a cryptic code like 0x80042108 or simply spins forever. Whether you rely on Outlook for work deadlines or everyday correspondence, a broken send/receive cycle means your inbox is effectively frozen.
This guide explains what causes an outlook send receive error, decodes the most common error codes, and walks you through eight fixes that resolve the vast majority of cases — from quick checks you can do in seconds to deeper repairs for stubborn failures. Every fix is safe to try and explained step by step.
How Outlook Send/Receive Works (and Why It Breaks)
Every time you click Send/Receive, Outlook contacts your mail server over the internet: the SMTP protocol carries your outgoing mail, while IMAP or POP3 delivers incoming mail to your inbox. The whole cycle depends on four things working together: an active internet connection, Outlook being in “online” mode, correct account and port settings, and healthy local data files.
When any one of these breaks, you get an outlook send receive error. The most common triggers are a dropped or misconfigured connection, Outlook accidentally switched to offline mode, wrong server ports, an oversized message jammed in the Outbox, antivirus software scanning your mail traffic, corrupted PST/OST data files, or — occasionally — a problem on your provider’s servers rather than on your computer.
Common Send/Receive Error Codes
Outlook usually reports failures with a hexadecimal error code. Decoding it immediately tells you where to look. Here are the codes you are most likely to encounter when diagnosing an outlook send receive error, what each means, and which fix to try first.
| Error code | Meaning | Try this fix first |
|---|---|---|
| 0x80042108 | Outlook cannot connect to the incoming (POP3/IMAP) server | Check internet connection and account settings |
| 0x80042109 | Outlook cannot connect to the outgoing (SMTP) server | Verify SMTP ports and authentication |
| 0x800CCC0F | Connection dropped while sending or receiving | Disable antivirus email scanning |
| 0x8004010F | Cannot access the Outlook data file | Repair data files with ScanPST |
| 0x8004060C | Incoming mail exceeds the size limit, or the data file is full | Remove the stuck oversized message from the Outbox |
| 0x800CCC79 | SMTP rejected the message (often a relay/authentication issue) | Enable outgoing server authentication |
| 0x800CCC92 | Login credentials rejected by the server | Re-enter your password and check account settings |
| 0x800CCC0E | Failed to connect to the server entirely | Check offline mode, then account settings |
Fixes: Resolving the outlook send receive error
Start with Fix 1 and work down. The early fixes take seconds and resolve most cases; the later ones handle the stubborn few.
Fix 1: Check your internet connection
It sounds obvious, but a flaky connection is behind more send/receive failures than any other cause. Open your browser and load a couple of websites. If pages are slow or failing, Outlook is not the problem — restart your router, reconnect to Wi-Fi, or switch networks, then try Send/Receive again.
Also worth checking: some VPNs and proxy servers block the mail ports Outlook needs. Temporarily disconnect your VPN and retry. If sending and receiving resumes, configure your VPN to allow SMTP (587/465) and IMAP (993) traffic, or whitelist Outlook in its settings, to keep the outlook send receive error away for good.
Fix 2: Check Outlook offline mode
Outlook has a “Work Offline” toggle that is embarrassingly easy to trigger by accident. Open the Send/Receive tab on the ribbon and look at the Work Offline button: if it appears pressed or highlighted, Outlook is deliberately disconnected and will not send or receive anything.
Click Work Offline to toggle back online, then click Send/Receive All Folders. Your stuck messages should start moving immediately. This single check resolves a surprising share of outlook send receive error reports.
Fix 3: Verify your account settings and ports
Wrong server settings are the classic cause behind a persistent outlook send receive error showing codes 0x80042108 and 0x80042109. Go to File > Account Settings > Account Settings, select your account, and click Change. Confirm your username (usually your full email address), then click More Settings > Advanced and check the ports:
- IMAP incoming: port 993 with SSL/TLS encryption.
- POP3 incoming: port 995 with SSL/TLS encryption.
- SMTP outgoing: port 587 with STARTTLS, or port 465 with SSL/TLS.
On the Outgoing Server tab, tick “My outgoing server (SMTP) requires authentication” and choose “Use same settings as my incoming mail server”. If your provider recently migrated you between server types (POP to IMAP, for example), settings from the old configuration will no longer work — check your provider’s current server names. For a deeper walkthrough of SMTP-specific failures, see our outlook SMTP error fix guide.
Fix 4: Repair your Outlook data files with ScanPST
When Outlook’s PST or OST data files become corrupted — usually after a crash, power cut, or forced shutdown — an outlook send receive error such as 0x8004010F is the result. Microsoft ships a free Inbox Repair Tool called scanpst.exe that fixes most damage.
- Close Outlook completely.
- Find scanpst.exe in your Office installation folder (typically under C:\Program Files\Microsoft Office\root\Office16).
- Run it and click Browse to select your data file — find its path under File > Account Settings > Data Files in Outlook first.
- Click Start to scan, then Repair if errors are found.
- Reopen Outlook and run Send/Receive.
For OST files (used with Microsoft 365 and Exchange accounts), you can also simply delete the OST file — Outlook rebuilds it from the server automatically. Never delete a PST file, though, if it is your only copy of POP3 mail.
Fix 5: Check the Outbox for stuck, oversized mail
A single huge attachment can block your entire Outbox and trigger an outlook send receive error: Outlook tries to send it, fails, and every message behind it waits forever. Open the Outbox folder in the folder pane. If you see a message sitting there — especially one with a large attachment — that is very likely your culprit.
To clear it, first switch Outlook to offline mode (Send/Receive > Work Offline) so it stops retrying. Then delete or move the stuck message, switch back online, and click Send/Receive All Folders. Resend the large file via a cloud link instead of an attachment — most providers also reject attachments above roughly 25 MB, so an oversized file will never send no matter how healthy Outlook is.
Fix 6: Disable antivirus email scanning
Antivirus suites that scan incoming and outgoing mail sit directly between Outlook and your mail server, and their integrations break send/receive more often than vendors admit — 0x800CCC0F is the classic symptom of an antivirus-triggered outlook send receive error. Open your antivirus settings and turn off email scanning (sometimes labelled “mail shield” or “email protection”).
Leave the antivirus’s real-time file protection on — you are only disabling the mail-traffic interception layer, which modern webmail filters and server-side scanning have largely made redundant. Restart Outlook and test Send/Receive. If it works, keep email scanning off and consider adding Outlook’s data files to the antivirus exclusion list instead.
Fix 7: Update Microsoft Outlook
Bugs in older Outlook builds cause an outlook send receive error that no settings change can fix. Open any Office app, go to File > Office Account > Update Options > Update Now, and install everything available. Restart your PC afterwards.
This is particularly worth doing if the error started suddenly with no settings changes on your part — a Windows update or a silent Office patch can introduce incompatibilities that the next update resolves.
Fix 8: Recreate your Outlook profile
If every other fix has failed, the profile itself — the container holding all your account settings — may be the hidden cause of your outlook send receive error. Creating a fresh one is safe because your mail re-syncs from the server.
- Close Outlook and open the Windows Control Panel.
- Search for Mail (Microsoft Outlook) and open it.
- Click Show Profiles > Add, name the new profile, and add your account.
- Set the new profile as the default with “Always use this profile”.
- Launch Outlook and confirm send/receive works.
You can delete the old profile afterwards. This is the same profile-reset technique that resolves the related family of cryptic Outlook malfunctions covered in our guide to outlook pii_email errors.
When the outlook send receive error Is Your Provider’s Fault
Not every outlook send receive error is Outlook’s fault. If none of the fixes above help — especially if the Outlook web app works fine or your other devices sync normally — the problem is likely server-side:
- Server outages: check your provider’s status page (for example, the Microsoft 365 service health dashboard) before spending more time troubleshooting.
- Password changes: if you recently changed your email password anywhere, Outlook keeps trying the old one and gets rejected (0x800CCC92). Re-enter the new password under Account Settings.
- Account limits: full mailboxes, exceeded sending quotas, or a suspended account all surface as send/receive failures. Sign in to webmail to check your quota and account status.
- Provider settings changes: providers occasionally change server names or drop support for older security protocols. If you use an older Outlook version, a provider-side change can silently break connectivity — check their support pages for updated settings.
- Firewall and network policies: on office or university networks, the network itself may block mail ports. If the same laptop works at home but fails at work, ask the network administrator rather than troubleshooting Outlook.
If your problems lean more towards delayed or missing incoming mail than outright send failures, our guide on how to fix Outlook sync issues covers that territory in detail.
Frequently Asked Questions
Why is Outlook not sending emails but receiving them?
This almost always points to the outgoing (SMTP) side: wrong SMTP port, missing outgoing-server authentication, or antivirus software blocking port 587. Receiving uses a completely separate connection, so it can work fine while sending fails. Work through Fix 3 (verify SMTP ports and authentication) and Fix 6 (disable antivirus email scanning) above.
What does error 0x80042108 mean in Outlook?
Error 0x80042108 means Outlook cannot connect to your incoming mail server (POP3 or IMAP), and it is one of the most reported outlook send receive error codes. The usual causes are no internet connection, Outlook set to Work Offline, or wrong incoming server settings and ports. Check your connection and offline mode first, then verify the account settings as described in Fix 3.
How do I fix emails stuck in the Outlook Outbox?
Switch Outlook to Work Offline (Send/Receive tab) so it stops retrying, then open the Outbox and delete or move the stuck message — large attachments are the usual cause. Switch back online and click Send/Receive All Folders. If a message keeps getting stuck, resend the file as a cloud-sharing link instead of an attachment.
Can antivirus software cause an outlook send receive error?
Yes, and it is one of the most common causes. Antivirus email-scanning modules intercept traffic between Outlook and your mail server, and when that integration breaks, send/receive fails — often with error 0x800CCC0F. Temporarily disable email scanning in your antivirus settings and retry; if it works, keep that module off and rely on real-time file protection instead.
Will rebuilding my Outlook profile delete my emails?
No. Recreating your profile removes only the local configuration; your emails, folders, and contacts stay on the mail server and re-download when the new profile syncs. The one exception is POP3 mail stored only in a local PST file — back that file up before making profile changes.
How do I know if the send/receive problem is my provider’s fault?
Sign in to the Outlook web app or your provider’s webmail on another device. If mail works there, the problem is on your PC and one of the fixes above applies. If webmail fails too, or your provider’s status page reports an outage, wait for them to resolve it — no amount of Outlook troubleshooting will help.