0x800CCC0E

Outlook error 0x800CCC0E: emails stuck in outbox fix

Software – Microsoft Office Intermediate 👁 10 views 📅 Jun 27, 2026

Error 0x800CCC0E usually means Outlook can't connect to your email server. The fix is almost always checking your outgoing server port settings or a wonky add-in. Let's get this sorted.

1. Wrong SMTP port or server name – the most common culprit

I've seen this error more times than I can count. Nine times out of ten, it's because Outlook has the wrong outgoing server port. Your ISP or email host changed something, and Outlook didn't update.

Here's the fix. Open Outlook, go to File > Account Settings > Server Settings. Click on your email account, then hit Change.

Look for Outgoing mail server (SMTP). The server name should match what your email provider uses. For Gmail, it's smtp.gmail.com. For Office 365, it's smtp.office365.com. For most others, check their support page.

Now the port. Click More Settings > Advanced. Under Outgoing server (SMTP), set the port to 587 and check TLS or STARTTLS. Some old providers still use port 25, but that's rare nowadays. Port 465 is for SSL, but most modern servers prefer 587 with TLS.

Don't bother with port 25 unless you know your host explicitly requires it. Most ISPs block port 25 to fight spam.

Click OK, then Test Account Settings. If it passes, you're done. If not, move to the next step.

2. Antivirus or firewall blocking – sneaky and common

Your antivirus thinks Outlook is suspicious. Or your firewall got updated and now blocks port 587. This happens all the time after a Windows update or antivirus definition update.

First, temporarily disable your antivirus – not just the notification, fully disable real-time protection. Then try sending an email. If it works, add Outlook as an exception in your antivirus. For Windows Defender, go to Windows Security > Virus & threat protection > Manage settings > Exclusions. Add OUTLOOK.EXE there.

If your company uses a corporate firewall, you might need to ask your IT team to allow outbound connections on port 587 (or whatever port your SMTP uses).

Also check if you're using a VPN. Some VPNs block SMTP ports. Disconnect the VPN and try again. If that fixes it, you'll need to adjust your VPN's split tunneling settings.

3. Outlook add-in or profile corruption – less common but real

Add-ins can mess with Outlook's network stack. I've seen Norton add-in, McAfee add-in, and even some PDF converters cause 0x800CCC0E.

Run Outlook in safe mode: hold Ctrl while clicking the Outlook shortcut. Or run outlook.exe /safe from the Run dialog (Win+R). If the error goes away in safe mode, disable add-ins one by one. Go to File > Options > Add-ins > Go at the bottom next to COM Add-ins. Uncheck all, then re-enable one at a time until the error comes back.

If safe mode doesn't help, your Outlook profile might be toast. Create a new profile: go to Control Panel > Mail > Show Profiles. Click Add, name it something like "newprofile", and set up your email again. Set it as default. This fixes corrupted data files that cause connection errors.

Still stuck? Run the Inbox Repair Tool (SCANPST.EXE). It's usually in C:\Program Files\Microsoft Office\root\Office16\ (or Office15 for 2016). Find your PST or OST file location from File > Account Settings > Data Files. Let SCANPST scan and fix it. This tool saved my bacon more than once.

4. Server-side issues – the one you can't control

Sometimes the email server itself has a problem. Maybe it's down, or the SMTP service is overloaded. Check your email provider's status page. For Office 365, check the Service Health dashboard in the admin center. For Gmail, check Google Workspace Status Dashboard.

Also check if your password changed or your account got locked. Outlook might show this error even if it's just an authentication problem. Go to File > Account Settings > Repair and re-enter your password.

Quick-reference summary table

CauseWhat to checkFix
Wrong SMTP portPort 587 with TLS? Server name correct?Set port to 587, use TLS
Antivirus blockingDisable AV, try sendingAdd Outlook as exception
Add-in conflictDoes safe mode work?Disable COM add-ins
Corrupt profileCreate new profileSwitch to new profile
Data file corruptionRun SCANPST.EXERepair PST/OST file
Server downCheck provider statusWait or contact support

That's it. Start with the SMTP port – that fixes most cases. If not, disable your antivirus next. Add-ins and profile corruption are less common, but I've seen them plenty. The table above gives you a quick path through each one.

Was this solution helpful?