Skip to content

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

Your vault is empty.

Free Fix 0x800CCC60

SMTP Protocol Errors 0x800CCC60 and 0x800CCC6F: Server Returns an Unexpected Reply

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

Fix it now

The connection worked, the conversation started, and then a reply arrived that Outlook could not act on. These are protocol complaints rather than credential or connectivity complaints, and the most common source is not the mail server – it is something in the middle answering on its behalf.

Confirm the submission port answers, substituting your own outgoing server

Test-NetConnection smtp.office365.com -Port 587
  1. Confirm the outgoing server name, port and encryption match the provider’s documentation exactly. For client submission to Microsoft 365 that is smtp.office365.com on port 587 with TLS.
  2. Turn off the security product’s outgoing mail scanning for one send. If the message goes, that component is answering on the server’s behalf and doing it badly.
  3. Test from a different network. Hotel, guest and some mobile networks intercept mail ports and produce exactly this.
  4. Check outgoing authentication is configured as the provider requires, in More Settings on the Outgoing Server tab.
  5. Send a small plain message with no attachment. If that succeeds where a larger one fails, the fault is in the transfer rather than in the handshake.

Move any failed message out of the Outbox into Drafts while you investigate. It retries on every cycle, and repeated failed submissions can trip rate limits at the provider.

If the message reaches Sent Items, you are done. If not, the next section explains where an out-of-sequence reply comes from.

Why it happens

Microsoft publishes no meaning for 0x800CCC60, 0x800CCC6F, 0x800CCC65, 0x800CCC67 or 0x800CCC62. The precise mappings you will find – one is a syntax error, one is a reply out of sequence, one is a command not implemented – are inference. They are plausible, and they are not something to act on without testing.

What is worth understanding is the shape. SMTP is a strict sequence of commands and numbered replies, and a client checks that each reply belongs to the class it expects and arrives at the point it expects it. Anything else it cannot recover from, so it abandons the transaction. That makes this family of failures a statement about the conversation rather than about your account.

The most common source of an out-of-sequence reply is not the mail server. It is something in the middle. Transparent proxies, captive portals, gateway appliances that inspect mail, and endpoint security products that proxy outgoing messages all speak on the server’s behalf. Some do it faithfully. Others return their own greeting banner, delay the greeting long enough for the client to move on, or send a reply before the client has finished speaking.

That is why the two most productive tests are switching off the local mail scanning component and moving to a different network. Between them they remove almost every device that can be answering on the server’s behalf, and if the message sends from a phone hotspot with the scanner off, you have narrowed the problem to two candidates in about four minutes.

Something is proxying the SMTP session

You have this one if Sending works with the security product’s mail component disabled, or from a different network.

  1. Disable outgoing mail scanning specifically and retest.
  2. If that fixes it, either leave that component off or configure the vendor’s documented exclusions for Outlook.
  3. On a corporate network, ask whether an inspecting mail gateway is in the path, and whether clients are supposed to submit to it directly rather than to the provider.

The wrong port for the service

You have this one if The account is submitting on a port that serves something else, or on one this network treats differently.

  1. Use the provider’s documented submission port. For Microsoft 365 that is 587 with TLS; port 25 is also accepted there but is the one most likely to be intercepted en route.
  2. Confirm the port answers with a connection test from the same machine.
  3. Apply, restart Outlook and send a test message.

Outgoing authentication does not match what the server expects

You have this one if The failure appears at the point in the conversation where authentication would happen, and receiving is unaffected.

  1. Tick the option requiring authentication on the Outgoing Server tab.
  2. Use the same credentials as the incoming server unless the provider documents separate ones.
  3. Untick secure password authentication unless it is specifically documented as required, since it is a mechanism most internet mail hosts do not implement.

The network is intercepting or redirecting mail ports

You have this one if It fails on guest wireless, in hotels or when tethered, and works normally elsewhere.

  1. Use the provider’s authenticated submission port rather than port 25, which is the one most often redirected.
  2. Where a captive portal is in use, complete the portal sign-in fully before sending anything.
  3. Connect through a VPN back to a trusted network if the local one insists on inspecting mail.

One specific message is the trigger

You have this one if A single message fails repeatedly while everything else sends normally.

  1. Move it out of the Outbox into Drafts so it stops retrying every cycle.
  2. Create it again as a new message rather than editing the failed copy.
  3. Remove and re-add the attachments, and check for an unusually long recipient list or an attachment type a gateway is likely to reject.
  4. Send the new copy and confirm it reaches Sent Items.

Full reference

Narrowing the search

Symptom Where the fault is
Fails on every send from one network only Something on that network is intercepting mail traffic
Started when a security product was installed or updated Its outgoing mail proxy
Only large messages fail The transfer stage rather than the handshake
Only fails while the VPN is connected Inspection on that route, or a different egress point
Started when the provider changed servers Settings, or a protocol version the client no longer offers
One specific message fails and others send The message, not the account

The four-minute test

  1. Move the failing message to Drafts so nothing is retrying in the background.
  2. Send a one-line message to yourself. If that works, the account is fine and the original message is the problem.
  3. If it fails, disable the security product’s outgoing mail scanning and send it again.
  4. If it still fails, connect to a phone hotspot and send it again.
  5. Whichever of those two changes made it work is your answer, and you have not touched a single setting in the account.

Submission settings worth checking against a source

Setting Microsoft 365 value
Server smtp.office365.com
Port 587 recommended; 25 also accepted
Encryption TLS or StartTLS enabled
Authentication Username or email address, and password

A failed message sitting in the Outbox retries on every send and receive cycle. That is worth stopping early: repeated failed submissions can trip rate limits at the provider and, on some hosts, look enough like abuse to get the account throttled.

Why a more tolerant client is not a fix

Some clients are more forgiving of odd replies and will complete a transaction that Outlook abandons. It is tempting to treat that as evidence that Outlook is the problem. It is not. The out-of-sequence reply is still being generated, whatever is generating it is still in the path, and it is still reading your mail on the way past. A client that ignores the anomaly has hidden it rather than removed it, and the next thing that anomaly breaks will be harder to trace.

When it really is the provider

  • Just after a platform migration, when host names or supported protocol versions changed and your settings did not.
  • When the provider retires an older transport security version and a client that only offers that version stops negotiating.
  • When a shared outbound host is under load and starts closing sessions early.
  • When a rate limit has been reached and the server is refusing further submissions from your account.
  • In each of those cases the tell is that it fails from every network and with all local scanning off, which is exactly what the four-minute test establishes.

Every code this article covers

Code What it points at Source
0x800CCC60 Seen where the server returned a reply Outlook could not act on. No published meaning; test with local mail scanning off and from a second network not published by the vendor
0x800CCC6F Seen where the transaction fails after it has started. No published meaning not published by the vendor
0x800CCC65 Seen in the same family, commonly read as a reply arriving out of the expected sequence. No published meaning not published by the vendor
0x800CCC67 Seen in the same family, commonly read as a command reported unavailable at that point. No published meaning not published by the vendor
0x800CCC62 Seen in the same family, commonly read as a syntax error returned against something the client sent. No published meaning not published by the vendor

Confirm the fix worked

  1. A message appears in Sent Items rather than sitting in the Outbox.
  2. The Outbox is empty after a full send and receive cycle.
  3. A larger message with an attachment also completes.
  4. The same test passes from a second network, which confirms the fix is in the settings rather than in the route you happened to be using.
  5. The security product’s remaining components are back on and mail still sends.

Questions people ask about this

Is this my mail provider’s fault?

Sometimes, particularly just after a platform change. More often it is something between you and them: a security product, an inspecting gateway or a network that redirects mail ports. Testing from a different network separates the two quickly.

Why does the same account send fine from webmail?

Webmail never uses SMTP from your machine. The browser talks to the provider over the web and the provider’s own systems inject the message, so everything this article is about happens on a path webmail does not use.

Would a different email client fix it?

Some clients are more tolerant of odd replies and will complete a transaction Outlook abandons. That hides the problem rather than fixing it, and whatever is generating the odd reply is still in the path and still reading your mail.

Is there anything to buy?

No. Correcting a port, an authentication setting or a scanner configuration costs nothing, and so does testing from another network. There is no product that makes a non-compliant reply compliant.

Do the individual codes tell me which stage failed?

Not dependably – Microsoft publishes no meanings for them, so the stage-by-stage table in circulation is inference. Use the practical test instead: scanner off, then a different network.

Related error codes

Was this article helpful?

Your feedback helps us improve our documentation.

Related articles

License Error Outlook 0x8004060C: The Mailbox or Outlook Data File Has Hit Its Size Limit Free Fix Office has detected a problem with this file: Protected View and File Block Rules Free Fix Office Crashes 0xc0000374 and 0xc0000409: Heap and Stack Corruption at Runtime License Error Outlook 0x800CCC90 and 0x800CCC92: POP3 Server Rejects Your Username or Password
โ† Back to Knowledge Base