Table of Contents
Last Updated
Do not index
IntroductionThe Most Common IMAP Errors and How to Fix Each OneHow to Check IMAP Connection SettingsPreventing IMAP IssuesOther Things You Need to Know About IMAP Errors
Introduction
IMAP errors occur when your email client fails to connect to the mail server, authenticate your credentials, or synchronize your mailbox state. The most common causes in 2026 are expired OAuth tokens after Gmail and Outlook retired basic password authentication, incorrect port configuration, mailbox storage limits, and server-side connection throttling. Each error points to a specific failure in the IMAP conversation between your client and the server, and knowing which error means what is the fastest path to a fix.
Most people encounter IMAP errors as vague messages in their email client: "Cannot connect to server," "Authentication failed," or "Connection timed out." These messages are frustratingly generic. The actual IMAP protocol returns specific error codes and responses that tell you exactly what went wrong, but most email clients don't surface them. Knowing where to look and how to interpret what you find turns a multi-hour troubleshooting session into a ten minute fix.
The Most Common IMAP Errors and How to Fix Each One
.png?table=block&id=33d16483-6d68-80cb-8846-f3c84b6ccab0&cache=v2)
- Authentication failed or Login failed
This is the most common IMAP error in 2026, and the cause is almost always the same: your email client is trying to authenticate with a username and password, but the server requires OAuth 2.0. Google eliminated basic authentication for IMAP in 2025. Microsoft completed the same transition for Exchange Online and Outlook.com shortly after.
If your email client was working fine for months and suddenly stopped connecting, check whether it supports OAuth. Thunderbird, Apple Mail, and recent versions of Outlook all support it natively. Older clients and third-party applications may need an update. If your client doesn't support OAuth at all, some providers still offer app-specific passwords as a fallback; check your account's security settings.
- Connection refused or Connection timed out
Your client couldn't establish a connection to the IMAP server at all. The three most common causes: wrong port number, firewall blocking the connection, or the server is down.
IMAP uses port 993 for encrypted connections (SSL/TLS from the start) and port 143 with STARTTLS. If your client is configured for port 110, that's POP3, not IMAP. Check your port settings first. If the port is correct, check whether your network's firewall or antivirus software is blocking outbound connections on that port. Corporate networks and some VPNs block non-standard ports. If port and firewall are both fine, the server may be experiencing downtime; check the provider's status page.
- Mailbox quota exceeded or Over quota
Your mailbox has hit its storage limit. IMAP keeps all messages on the server, and when storage runs out, the server stops accepting new mail and may reject sync requests. Gmail provides 15GB shared across Gmail, Drive, and Photos on free accounts; Google Workspace accounts typically have 30GB to unlimited depending on the plan.
The fix is straightforward: delete old emails, empty your trash, and clear your spam folder. Large attachments are usually the biggest storage consumers. Search for emails with large attachments and delete or archive them first for the fastest storage recovery.
- Too many simultaneous connections
IMAP allows multiple clients to connect to the same account simultaneously, but servers impose connection limits. Gmail allows 15 simultaneous IMAP connections. If you have your phone, laptop, tablet, a desktop email client, and a third-party application all connected to the same account, you may hit this limit.
Close email clients on devices you're not actively using, or configure less-used clients to check for new mail less frequently. Some clients open multiple IMAP connections per account (one per folder being monitored), which can consume the limit faster than expected.
- IMAP server does not support the requested operation
The command your client sent isn't supported by the server's IMAP implementation. This usually happens with older or non-standard IMAP servers that don't support modern extensions like IDLE (real-time push notifications) or CONDSTORE (change tracking for efficient sync).
If you're connecting to a major provider (Gmail, Outlook, Yahoo), this error is rare. On self-hosted or legacy mail servers, it's more common. Check your client's IMAP settings for options to disable specific extensions or use a compatibility mode.
- Selected mailbox does not exist
Your client is trying to access a folder that doesn't exist on the server. This happens after folder renames, deletions, or when your client's local folder mapping doesn't match the server's current structure. Rebuilding the IMAP folder subscription list in your client settings usually resolves it. In Thunderbird, right-click the account and select "Subscribe" to refresh the folder list. In Apple Mail, go to Mailbox > Rebuild.
- Sync errors and duplicate messages
Messages appearing multiple times or read/unread status not syncing properly usually indicate a corrupted local cache. IMAP clients maintain a local copy of folder state; when that cache gets out of sync with the server, weird behavior follows. The fix is rebuilding the local cache. In most clients, this means removing the account and re-adding it, or finding the "Rebuild" or "Reset Sync" option in settings.
How to Check IMAP Connection Settings
Every email provider publishes their IMAP server settings. Here are the ones you'll use most often:
- Gmail: imap.gmail.com, port 993, SSL/TLS, OAuth 2.0 required.
- Outlook/Hotmail: Outlook.office365.com, port 993, SSL/TLS, OAuth 2.0 required.
- Yahoo: imap.mail.yahoo.com, port 993, SSL/TLS.
For Google Workspace and Microsoft 365 business accounts, the server addresses are the same as the consumer versions. Custom domains route through the same infrastructure.
Preventing IMAP Issues
- Keep your email client updated: OAuth support, security patches, and IMAP compatibility improvements ship in updates. An outdated client is the most common source of authentication failures.
- Monitor your mailbox storage: Set up alerts or check quarterly. A mailbox at 95% capacity causes intermittent sync failures before it hits 100% and stops accepting mail entirely.
- Use port 993 exclusively: This port is encrypted from the first byte onward and is supported by every modern provider. Port 143 with STARTTLS works but adds an unnecessary step and is increasingly unsupported.
- Limit simultaneous connections: If you have five devices connected to one account and experience intermittent disconnections, reduce the number of active clients or adjust polling intervals.
Other Things You Need to Know About IMAP Errors
My email client says "connected" but new emails aren't appearing.
Your client may be connected but not actively checking for new mail. Check whether IMAP IDLE (push notifications) is enabled. Without IDLE, your client polls the server at intervals (every 5 to 15 minutes). If IDLE is enabled and emails still aren't appearing, the server may be experiencing delivery delays unrelated to IMAP.
Can IMAP errors cause me to miss important emails?
Yes. If your client can't connect to the server, you won't see new messages until the connection is restored. If a storage quota is exceeded, new emails may bounce back to the sender entirely. IMAP errors on the receiving side don't affect your sending, but they can prevent you from seeing replies and inbound messages.
Should I switch to a web client if I keep getting IMAP errors?
Web clients (Gmail's browser interface, Outlook on the web) bypass IMAP entirely and connect to the mail server through proprietary APIs. If IMAP is causing persistent problems and you don't need a desktop client, the web interface is the most reliable option.