Skip to content

Est. 2011ยทMicrosoft Partner ID 7033487ยทDelivery under 3 minยทSupport 7 days a week

Your vault is empty.

Free Fix 0x800CCC80

Outlook 0x800CCC80 and 0x800CCC1A: SSL and Authentication Method Mismatch on Send

11 min read Updated October 5, 2026 Outlook & Office Applications

Fix it now

These are negotiation failures rather than password failures. Client and server could not agree on how the conversation is encrypted, or on how you prove who you are, and both are settings on the client side of a server that is behaving as documented. The port and the encryption type have to match each other, not merely be individually plausible.

Confirm both ports answer, substituting your own provider’s servers

Test-NetConnection outlook.office365.com -Port 993
Test-NetConnection smtp.office365.com -Port 587
  1. Open the account’s More Settings and then the Advanced tab, and read the port numbers and the encryption dropdowns together. For Microsoft 365 that is IMAP 993 with SSL/TLS, POP 995 with SSL/TLS, and SMTP submission on 587 with STARTTLS.
  2. Untick the secure password authentication option in the incoming logon settings, and check the Outgoing Server tab for the same option. It is a specific mechanism that most internet mail hosts do not implement, and it is the usual reason no method is common to both ends.
  3. If a certificate warning appears, read the subject and the issuer before dismissing it. A name that does not match, an expired certificate and a wrong clock on this machine all look identical from here.
  4. Apply, close every dialog, restart Outlook and run a send and receive.

A certificate issued by a locally installed security product means that product is intercepting the session. Turn its encrypted mail scanning off and retest before you accept anything.

If the cycle completes with no certificate prompt and no error, you are done. If not, the next section separates the two negotiations that can fail here.

Why it happens

Microsoft publishes no meaning for 0x800CCC80, 0x800CCC7D, 0x800CCC1A, 0x800CCC01 or 0x800CCC02. The versions in circulation – one of them is the certificate contents, another is the certificate dates – are inference. What is documented, and what you can check, is the settings each provider expects, and that is where this is fixed.

Every mail session settles two questions before a message moves. The first is how the conversation is encrypted. Implicit encryption starts from the first byte on a dedicated port; explicit encryption starts in the clear on an ordinary port and is upgraded by a command. Point a client set to one shape at a port serving the other and neither side can parse what arrives. That is why the port and the encryption dropdown have to be read as a pair.

The second question is authentication, and it has its own list: a plain password inside an encrypted channel, an integrated Windows mechanism, a token from an identity provider, or the specific mechanism Outlook labels secure password authentication. A failure here means the intersection of what the client offered and what the server accepts was empty. Ticking that last option in the belief that it makes the connection safer is the most reliable way to create that empty intersection.

Certificates are the third thing that presents as a negotiation failure without being one. The name the certificate covers has to match the host name you typed, the certificate has to be within its validity dates, and the machine’s own clock has to be right – because a workstation with the wrong date will reject a perfectly valid certificate and produce an identical symptom. Check the clock before you conclude the provider has a problem.

The encryption type and the port do not match

You have this one if The failure is instant, and the settings differ from what the provider documents even slightly.

  1. Take the provider’s documented values and enter them exactly rather than adjusting what Outlook auto-configured.
  2. Do not mix the two shapes. Implicit encryption belongs on the dedicated encrypted ports; STARTTLS belongs on the ports that support an upgrade.
  3. Apply, close all dialogs, restart Outlook, and test the incoming and outgoing servers separately.

Secure Password Authentication is enabled and the server does not offer it

You have this one if The credentials are known to be correct and the failure is immediate and consistent.

  1. Untick the secure password authentication option in the incoming logon settings.
  2. Check the Outgoing Server tab for the same option and untick it there too.
  3. Confirm the connection is still encrypted through the port and encryption settings, which are separate from this option.
  4. Restart Outlook and test.

Turning this off does not send your password in the clear, provided the connection itself is encrypted. Those are two different settings that are easy to confuse.

The certificate does not cover the host name you typed

You have this one if A certificate warning names a host different from the one in the account settings.

  1. Use exactly the host name the provider documents, which is frequently their own name rather than a name in your domain.
  2. If you must use a name in your own domain, the provider has to issue a certificate covering it. There is no client-side workaround.
  3. Read the issuer as well as the subject. A certificate issued by a locally installed security product means that product is reading the session.

The workstation clock is wrong

You have this one if A certificate is rejected on this machine while the same server works from others.

  1. Open Settings, then Time and language, then Date and time, and synchronise the clock.
  2. Correct the time zone as well as the time. A right clock in the wrong zone still validates certificates incorrectly.
  3. On a domain-joined machine, confirm it is following the domain time hierarchy rather than a stale manual source.
  4. Retest. No Outlook change is needed once the clock is right.

Something is intercepting the encrypted session

You have this one if The certificate presented is issued by a security product, a gateway appliance, or something you do not recognise.

  1. Turn off the product’s encrypted mail scanning and retest.
  2. If that resolves it, either leave the component off or apply the vendor’s documented exclusions.
  3. On a corporate network, ask whether an inspecting gateway is deliberately in the path before you work around it.

Full reference

Reading the symptom

Symptom Where the fault is
Fails immediately on the incoming server The encryption type does not match the incoming port
Receives fine, fails only on send The outgoing port, its encryption, or outgoing authentication
A certificate warning appears before the error Name mismatch, expiry, interception, or a wrong clock on this machine
Started working after unticking secure password authentication That mechanism was never supported by the server
Fails on this machine only The clock, or something installed locally that is inspecting the session

The settings that can be checked against a published source

Service Microsoft 365 value
IMAP outlook.office365.com, 993, SSL/TLS
POP outlook.office365.com, 995, SSL/TLS
SMTP, client smtp-mail.outlook.com, 587, STARTTLS
SMTP AUTH client submission smtp.office365.com, 587 recommended, TLS enabled
Secure password authentication Off, unless your provider documents that it is required

Other ports exist and are widely used – implicit encryption on an alternative SMTP port, and STARTTLS on the plain IMAP and POP ports – but take those numbers from your own provider’s documentation rather than from a general article, because which of them a given host offers varies and a wrong pairing is precisely the fault this article is about.

Do not permanently accept a certificate you cannot account for. A name that does not match is sometimes a provider using a shared certificate, and is sometimes a device between you and the server reading your mail. Read the issuer and the subject before deciding, and if you cannot explain either, stop and ask whoever runs the network.

Working through it in order

  1. Write down what the account is currently set to, so you can put it back.
  2. Get the provider’s documented values and set them exactly, incoming and outgoing.
  3. Untick secure password authentication in both places unless it is specifically documented as required.
  4. Restart Outlook completely rather than closing a dialog, since some settings are only re-read at start.
  5. Test receiving and sending separately, so a single failure does not obscure a fix that worked.
  6. Only if a certificate warning appears, read it in full – subject, issuer, dates – before doing anything else.

Why this starts on a day when nothing changed

  • Certificates expire on a schedule and are replaced with ones covering slightly different names.
  • Providers retire older protocol versions and authentication mechanisms with little notice to end users.
  • A security product updates and switches its encrypted mail scanning back on.
  • A machine’s clock drifts, or its time source stops being reachable, and certificate validation starts failing.
  • An account that was auto-configured years ago is still carrying settings the provider stopped supporting, and only fails when the last fallback is removed.

In every one of those cases the client did not change, which is exactly why people look at the client for so long. The question worth asking early is not “what did I change” but “does this machine’s configuration still match what the provider currently publishes”.

Every code this article covers

Code What it points at Source
0x800CCC80 Seen where no authentication method was common to client and server. No published meaning; check the secure password authentication option first not published by the vendor
0x800CCC7D Seen where a secure connection could not be established. No published meaning not published by the vendor
0x800CCC1A Seen where the encrypted session could not be negotiated on that port. No published meaning; read the port and the encryption setting as a pair not published by the vendor
0x800CCC01 Seen alongside a certificate validation failure. No published meaning; read the certificate’s subject and issuer not published by the vendor
0x800CCC02 Seen alongside a certificate validation failure. No published meaning; check the certificate dates and this machine’s clock and time zone not published by the vendor

Confirm the fix worked

  1. A send and receive completes with no certificate prompt and no error.
  2. Test-NetConnection returns True for both the ports you configured.
  3. Every setting matches the provider’s documentation field by field, rather than merely working today.
  4. Outlook is closed completely and reopened, and no prompt returns on a cold start.
  5. The machine’s clock and time zone are correct and synchronising, so certificate validation is not depending on luck.

Questions people ask about this

Is SSL the same as TLS in these settings?

The labels describe the shape rather than the protocol version. One means encryption from the moment the connection opens on a dedicated port; the other means starting in the clear and upgrading. Modern transport security is used underneath either way.

Can I just set encryption to None to get working again?

You can, and your password then crosses the network readable by anything in the path. Most providers refuse plain-text logon anyway. Treat it as a diagnostic step of a few seconds and change it straight back.

Why did this start when nothing changed on my machine?

Because the server moved. Certificates expire, providers rotate host names and retire authentication mechanisms, and a security product can switch a component back on during an update. From the client’s point of view nothing changed, and that is exactly the point.

Is there anything to buy here?

No. Every fix is a setting. If your own mail server presents a mismatched or expired certificate, a correctly issued certificate is a real cost, but it belongs on the server and no Microsoft or antivirus licence affects it.

What do the codes actually mean?

Microsoft does not publish meanings for any of them. Use them to tell certificate trouble from negotiation trouble – a certificate warning appearing first is the useful signal – and then work from the provider’s documented settings.

Related error codes

Was this article helpful?

Your feedback helps us improve our documentation.

Related articles

License Error Outlook 0x80070020: The OST File Is In Use and Locked by Another Process License Error Unlicensed Product 0xC004F017 in Word, Excel, Visio and Project: Activation Failed Free Fix Outlook Certificate Errors 0x80072F0D and 0x800B0109: Untrusted or Mismatched SSL License Error Send/Receive Timeouts 0x8004210A and 0x8004210B: Outlook Gives Up Waiting on Server
โ† Back to Knowledge Base