Outlook Error 0x800CCC0E: What It Means and How to Fix

Outlook error 0x800CCC0E appears when Outlook tries to reach your mail server and the underlying TCP connection never opens. The Send/Receive dialog shows the error code alongside a message that varies by account setup — sometimes 'cannot connect to the server,' sometimes a raw socket failure. Either way, the problem is the same: Outlook cannot establish the channel it needs to retrieve or send mail.

Three causes account for nearly every instance of this error. The account settings specify the wrong port or the wrong encryption type, so the server refuses the connection. An ISP is silently blocking port 25, the old mail submission port that most residential and business connections filter to prevent spam. Or local security software — an antivirus or firewall — is intercepting and corrupting the encrypted mail session. The fix depends on which one you have, and this guide works through all three.

What Outlook error 0x800CCC0E actually means#

The code 0x800CCC0E maps to a TCP-layer failure: Outlook sent a connection request to the IP address and port in your account settings, and nothing answered. No TLS handshake, no server greeting — the socket timed out or was refused before any mail protocol ran.

Because the failure is at the network layer, not at the authentication or mailbox layer, the error can appear on both incoming (IMAP or POP3) and outgoing (SMTP) accounts. When you send a message and get 0x800CCC0E, Outlook could not open the SMTP submission connection. When you receive it during sync, the IMAP or POP3 connection is what failed. The account settings dialog in Outlook shows IMAP and SMTP as separate entries — each has its own server address, port, and encryption setting, and each can produce this error independently.

Causes, how to confirm, and what to fix#

The table below maps the four main causes to a confirmation test and a fix. Run the confirmation test before changing settings — it tells you whether you are solving the right problem.

Fix 1: Correct the port and encryption settings#

Wrong port or encryption is the most common cause of 0x800CCC0E and the fastest to fix. The server simply never responds on an unexpected port — port 143 with SSL encryption looks identical to Outlook as a server that is down, because the server will not open the session without the negotiation it expects.

Your mail provider publishes the correct settings in its help documentation. Confirm them before editing, because the values vary by provider and the encryption type determines whether the port should be 993 or 143 for IMAP, and whether SMTP takes STARTTLS or SSL.

1. 1

   Open Account Settings

   In Outlook, go to File, then Account Settings, then Account Settings again. Select the affected email account and click Change.

2. 2

   Click More Settings, then open the Advanced tab

   The Advanced tab shows the incoming server port (IMAP or POP3) and the outgoing server port (SMTP), each with an encryption dropdown alongside it.

3. 3

   Set the incoming server port

   For IMAP with SSL/TLS, set the port to 993 and the encryption to SSL/TLS. Port 143 is the unencrypted IMAP port — most providers no longer accept it for authenticated connections.

4. 4

   Set the outgoing server port

   For SMTP with STARTTLS, use port 587 and set encryption to STARTTLS. For SMTP with implicit SSL, use port 465 and set encryption to SSL/TLS. Avoid port 25 for end-user submission — ISPs filter it to block outbound spam.

5. 5

   Save and test

   Click OK, then Next, then Finish. Back in the main Outlook window, click Send/Receive. If the connection succeeds, the error is resolved. If it returns, proceed to Fix 2 or Fix 3.

Fix 2: Work around an ISP blocking port 25#

Many residential and business ISPs filter outbound port 25 at the network level to limit spam from compromised machines on their network. Outlook gives no specific indication this is happening — from its perspective, the connection simply times out, producing 0x800CCC0E. The test takes under a minute: change your SMTP port to 587 and attempt to send.

If the error clears on 587, port 25 was the block and you are done. If you are on an infrastructure that still requires port 25 for server-to-server relay, that is a separate issue and not something a client-side Outlook setting can fix. For end-user submission, 587 or 465 is always the right answer.

1. 1

   Open your SMTP account settings

   In Outlook, go to File, then Account Settings, then Account Settings. Select the account, click Change, then More Settings, then the Advanced tab.

2. 2

   Change the SMTP port from 25 to 587

   Enter 587 in the outgoing server port field. Set the encryption type to STARTTLS (also listed as Auto in some Outlook versions).

3. 3

   Attempt to send a test message

   Click OK and close the settings dialogs. Compose a short message to yourself or a colleague and send it. A successful send confirms port 25 was the block.

4. 4

   If 587 also fails, try 465

   Some providers accept outbound submission only on port 465 with implicit SSL. Change the port to 465 and set the encryption to SSL/TLS, then attempt the send again.

Fix 3: Stop antivirus mail scanning from intercepting the session#

Antivirus products that scan email intercept the SSL/TLS session between Outlook and your mail server to inspect content in transit. When the antivirus certificate is not trusted by Outlook, or when the interception corrupts the TLS handshake, Outlook sees the same result as a closed port: the TCP connection fails to establish cleanly, and 0x800CCC0E appears. This is the cause most threads never confirm because it looks identical to a genuine server outage.

The isolation test is simple and takes under two minutes. Disable the antivirus email scanning module — not the full antivirus — and immediately attempt a Send/Receive. If the error clears, you have confirmed the interceptor is the cause. Re-enable the full antivirus protection after the test, then configure a permanent exception rather than leaving mail scanning off.

1. 1

   Open your antivirus settings

   Find the email scanning, mail protection, or SMTP/POP3 scanning section. Common locations vary by product: look for Mail Shield, Email Protection, or Online Threat Prevention depending on what you have installed.

2. 2

   Pause or disable the mail scanning feature only

   Disable the email or SMTP scanning component, not the full real-time protection. This is a diagnostic step, not a permanent change.

3. 3

   Test Send/Receive in Outlook

   With mail scanning paused, attempt a Send/Receive. If mail flows and 0x800CCC0E is gone, the antivirus interception is confirmed as the cause.

4. 4

   Add Outlook as a trusted process or disable SSL scanning for mail

   In the antivirus settings, add OUTLOOK.EXE and optionally the mail server hostname as trusted, or permanently disable the SMTP/IMAP SSL scanning feature. Re-enable full real-time protection after making the exception.

5. 5

   Check Windows Firewall if the antivirus is not the issue

   If disabling the email scanning module makes no difference, open Windows Defender Firewall and confirm Outlook has outbound access on the ports you configured. An overly strict outbound rule produces the same TCP failure as a closed server port.

How to tell which cause you have#

If you are not sure which of the three causes applies, run this isolation sequence in order. It takes about five minutes and avoids changing settings that do not need changing.

First, check your port and encryption settings against your provider's published table. If they are wrong, fix them and test — you are done. If they are already correct, the error is not a settings mismatch.

Second, try changing your SMTP port to 587 if it is currently set to 25, or to 465 if 587 also fails. A successful send at 587 tells you ISP port blocking was the cause.

Third, if the settings are correct and the port change made no difference, pause your antivirus mail scanning and test immediately. If the error clears, the interceptor is the cause and you need a permanent antivirus exception.

If all three tests come back negative — settings correct, alternative ports fail, disabling antivirus changes nothing — the server itself may be unreachable. Check your provider's status page for an outage, then ping the mail server hostname to confirm it resolves and responds. A non-resolving hostname means a DNS problem. A hostname that resolves but does not respond to a TCP connection indicates a server-side outage on that port.

Preventing 0x800CCC0E from coming back#

The error rarely returns once the root cause is fixed, but a few habits reduce the risk. Keep your mail provider's server settings bookmarked. Providers occasionally change their SMTP or IMAP hostnames — particularly after infrastructure migrations — and when they do, existing Outlook accounts lose connection until the settings are updated.

If your antivirus auto-updates, periodically recheck that the mail exception you configured still applies. Major antivirus updates sometimes reset custom exclusions and re-enable SSL scanning with a stricter certificate policy. A sudden return of 0x800CCC0E after a software update is almost always this.

For outgoing mail, use port 587 with STARTTLS as the standard — ISPs are far less likely to filter it than port 25. If you ever move to a new ISP, verify the SMTP port works on the new connection before assuming old settings carry over.

Where AI Emaily fits#

The 0x800CCC0E error is a product of Outlook managing the mail server connection directly, with all the port-setting and antivirus-interception complexity that brings. AI Emaily connects to Gmail, Outlook and IMAP mailboxes through a server-side layer, so the TLS negotiation, port selection, and reconnection on failure happen infrastructure-side rather than on your machine. There is no local antivirus to intercept the session and no per-account port to misconfigure. We build AI Emaily, and it comes with a 7-day free trial on the Pro and Autopilot plans.