Fix it now
Either the IMAP server refused the logon or it ended a session that had already started. IMAP holds connections open per folder and leaves the server authoritative, so it fails in ways POP does not – and a wrong root folder path produces a logon that looks broken but is not.
- Confirm the credentials in the provider’s webmail before changing anything in Outlook.
- Clear the stored credential: Credential Manager, Windows Credentials, remove entries for the mail host, then restart Outlook and let it prompt.
- Check the incoming settings. For Microsoft 365 that is outlook.office365.com on port 993 with SSL/TLS and OAuth 2.0 modern authentication.
- Check the root folder path in More Settings, Advanced. Some hosts need INBOX there and others need it blank, and a wrong value gives you a logon that appears to work with a folder tree that does not.
- Reduce the number of open sessions: close Outlook on other machines, and unsubscribe from folders you do not need. Then restart Outlook and let it rebuild the folder list.
If the mailbox is in Microsoft 365, basic authentication for IMAP is disabled in all tenants. Adding the mailbox as a Microsoft 365 or Exchange account rather than an IMAP account removes this whole class of problem.
If the folder tree matches webmail and stays connected, you are done. If not, the next section explains why IMAP fails differently from POP.
Why it happens
Microsoft publishes no meaning for 0x800CCCD1, 0x800CCCD2, 0x800CCCD3 or 0x800CCCDD, so the crisp definitions in circulation are inference. The behaviour of IMAP, on the other hand, is well understood, and it explains most of what people see here better than a code table would.
POP collects mail and disconnects. IMAP keeps the server authoritative and holds connections open per folder so it can be told about changes as they happen. A busy mailbox with many subscribed folders, open on a desktop, a laptop and a phone at once, uses a lot of simultaneous connections. Hosts cap that number per mailbox and close the extras without ceremony. From the client’s side that looks like the server dropping you for no reason.
The root folder path exists because IMAP servers differ over where the mail folders sit relative to the account’s namespace. Set it wrongly and the client authenticates successfully and then asks for folders beneath a path that does not exist, or beneath one that nests everything under the inbox. The logon worked; everything after it did not. This is why the symptom is so often misread as an authentication problem, and it is worth checking before you touch a password.
Then there is whether IMAP is available at all. In Exchange Online, support for POP3 and IMAP4 is enabled by default when a mailbox is created, so if it is off somebody turned it off – and it is a per-mailbox setting, which is why a colleague’s working account proves nothing about yours. Separately, Microsoft has removed the ability to use basic authentication in Exchange Online for IMAP among other protocols, and states that basic authentication is now disabled in all tenants. A client offering a plain password there will be refused however correct the password is.
IMAP is switched off for this mailbox
You have this one if The credentials are known good, webmail works, and only the IMAP connection is refused – consistently, not intermittently.
- Ask the administrator to check the mailbox specifically. In the Exchange admin centre: Recipients, Mailboxes, select the mailbox, then on the General tab open Manage email apps settings under Email apps & mobile devices.
- For an Outlook.com account, POP and IMAP access is off by default and is turned on in the account’s own mail settings.
- If the mailbox lives in a Microsoft 365 tenant, consider removing the IMAP account and adding the mailbox as a Microsoft 365 account, which sidesteps the protocol entirely.
The client is offering a plain password where none is accepted
You have this one if The mailbox is in Microsoft 365, other clients work, and only the IMAP account is refused.
- Stop trying to make the password work. Basic authentication is disabled in all Exchange Online tenants for IMAP.
- Add the mailbox as a Microsoft 365 or Exchange account, which uses modern authentication.
- Where IMAP is genuinely required, the client itself must support OAuth 2.0 for IMAP – Microsoft released that support in 2020, and a client without it has no route.
A stale credential is being resubmitted
You have this one if There is no prompt at all, just an immediate rejection, and the password changed recently.
- Remove the mail entries from Windows Credentials in Credential Manager.
- Clear and reset the remember-password option in the account so a fresh credential is stored.
- Restart Outlook and enter the current password.
- Check every other device with the same account configured, because one of them retrying the old password can lock the account repeatedly.
The root folder path is wrong
You have this one if The account connects, and the folder tree is empty, duplicated, or oddly nested beneath the inbox.
- Set the root folder path to INBOX or leave it blank, according to what the provider documents.
- Apply, restart Outlook and allow the folder tree to rebuild before judging the result.
- If duplicated folders remain after the rebuild, confirm the mail is present in webmail, then remove and re-add the account.
Too many simultaneous connections to the mailbox
You have this one if It works briefly and then drops, and the same mailbox is open on more than one client at once.
- Close other clients and test with one only, to confirm the diagnosis.
- Right-click the account in the folder list, choose IMAP Folders, and subscribe only to the folders you actually need.
- Lengthen the send and receive interval so cycles do not overlap.
- Never run two Outlook profiles against the same IMAP mailbox on one machine.
Full reference
Matching symptom to cause
| Symptom | Where the fault is |
|---|---|
| The password prompt repeats and is rejected | The credential, or IMAP disabled or basic-auth-blocked for that mailbox |
| Logon succeeds but no folders appear | The root folder path |
| Works for a few minutes then drops | A connection limit, or an idle timeout on the path |
| Only some folders synchronise | Folder subscription, or one very large folder |
| Duplicated folders nested under Inbox | The root folder path is set when it should be blank |
| Fails only on this machine | Local interception, the profile, or the local data file |
Settings you can check against a source
| Setting | Microsoft 365 value |
|---|---|
| Server | outlook.office365.com |
| Port | 993 |
| Encryption | SSL/TLS |
| Authentication | OAuth 2.0 modern authentication |
| Protocol availability | Enabled by default per mailbox; disabled only by an administrator |
Note that last row, because it inverts the usual assumption. In Exchange Online the protocol is on unless somebody switched it off, so “IMAP is probably disabled” is a hypothesis to test rather than a conclusion. For an Outlook.com account the default runs the other way and the protocol has to be turned on first.
Before you remove and re-add an IMAP account, confirm that everything you care about actually exists on the server. Items in local-only folders, drafts that never synchronised, and anything in an attached data file are not part of the IMAP mailbox and will not come back by themselves. Check in webmail first, and copy anything local somewhere safe.
Reducing the connection count
- List every device and client that has this mailbox open, including phones and a second computer.
- Close all but one and confirm the problem disappears. That is the test; everything after it is tidying.
- Right-click the account in Outlook’s folder list, choose IMAP Folders, and unsubscribe from folders nobody reads.
- Lengthen the automatic send and receive interval so one cycle finishes before the next begins.
- Bring the other devices back one at a time and watch for the point at which it breaks again.
When the folder tree is the symptom
- An empty tree after a successful logon is almost always the root folder path, not the credential.
- Folders nested one level too deep, all under Inbox, means the path is set where it should be blank.
- Folders missing rather than misplaced means subscription: Outlook shows only folders you are subscribed to.
- A tree that matches webmail but does not update means synchronisation rather than logon, and the connection count is the first thing to look at.
- A tree that rebuilds differently every restart usually means two clients fighting over the same subscriptions.
Whether IMAP is the right shape at all
IMAP is the right answer for a mailbox read on several devices where the server should hold the authoritative copy. It is not the right answer for a Microsoft 365 mailbox that could be added as a full account, because that gives you calendar, contacts and shared folders as well as mail, uses modern authentication, and does not have a per-folder connection budget to run out of. If you are configuring IMAP against Microsoft 365 today, it is worth asking why.
Every code this article covers
| Code | What it points at | Source |
|---|---|---|
0x800CCCD1 |
Seen when the IMAP server refuses the logon. No published meaning; check the credential, the protocol’s availability and the authentication method | not published by the vendor |
0x800CCCD2 |
Seen where the server’s reply was not one the client could act on. No published meaning | not published by the vendor |
0x800CCCD3 |
Seen in the same circumstances during an IMAP session. No published meaning | not published by the vendor |
0x800CCCDD |
Seen when the server closes a session that had already started. No published meaning; connection count and idle timeouts are the first things to check | not published by the vendor |
Confirm the fix worked
- The folder tree in Outlook matches the one in webmail.
- A message sent to the mailbox appears in Outlook within one synchronisation interval.
- A message moved between folders in Outlook is reflected in webmail.
- Outlook is closed, reopened, and the session establishes without a credential prompt.
- The account stays connected for a working day rather than dropping after a few minutes.
Questions people ask about this
Should I be using IMAP or POP?
If you read mail on more than one device, IMAP or a full account is the right shape, because the server holds the authoritative copy and every device sees the same state. POP suits a single machine that wants mail stored locally and nowhere else.
Why do deleted items show with a line through them?
That is IMAP behaving as designed. An item can be marked for deletion without being removed until the folder is purged. Outlook can be configured to move deletions to a Deleted Items folder instead, which most people find less confusing.
Will re-adding the account delete my mail?
Mail held on the server is safe and will resynchronise. Anything that exists only locally is not part of the mailbox and will not come back, so check for local-only folders and attached data files first.
My colleague’s IMAP works and mine does not. Why?
Because it is a per-mailbox setting. In Exchange Online the protocol is enabled by default on each mailbox and disabled individually, so one working account tells you nothing about another.
Is there anything to buy to fix this?
No. If IMAP is disabled for your mailbox, that is a setting an administrator changes at no cost. If the host has withdrawn the authentication method you were using, moving the mailbox elsewhere is a commercial decision about hosting rather than a repair you can buy for Outlook.
