143 IMAP TCP Flagship
Reference for TCP port 143, commonly associated with IMAP.
What it's for
Port 143 is the default port for IMAP (Internet Message Access Protocol) — the dominant modern protocol for retrieving and managing email. Unlike POP3, IMAP keeps your mailbox on the server as the source of truth: messages, folders, read/unread status, and flags all stay synchronized there, and every device (phone, laptop, webmail) sees a consistent, up-to-date view.
This server-centric model is exactly why IMAP replaced POP3 as the default for most providers — checking mail from multiple devices without losing sync or accidentally deleting messages from other devices was a real pain point POP3 never solved well.
Protocol basics
- Protocol: TCP, needed for reliable folder/message synchronization.
- Server-authoritative state. Folders, message flags (read, flagged, deleted), and even partial message fetches (headers only, or a specific attachment) are all managed server-side, letting clients stay lightweight and in sync.
- Plaintext by default on port 143. Like POP3, the base IMAP port is unencrypted; STARTTLS can upgrade an existing connection, or clients can connect directly to port 993 (IMAPS) for implicit TLS from the start.
- Supports partial fetches. A mobile client can request just message headers or a preview snippet rather than downloading a full message with attachments, which is part of why IMAP works well on bandwidth-constrained connections.
Security considerations
- Avoid plain IMAP (port 143) on untrusted networks. Credentials and message content are unencrypted unless STARTTLS is negotiated — prefer port 993 (IMAPS) for guaranteed encryption from the first byte.
- App-specific passwords are increasingly required by major providers (Gmail, Outlook) when 2FA is enabled, since IMAP's basic authentication doesn't support modern MFA flows natively — OAuth2-based IMAP authentication is the more secure modern alternative where supported.
- Server-side mailbox access means a compromised IMAP credential exposes your entire mail history, not just newly downloaded messages — unlike POP3's download-and-delete model, everything remains accessible via IMAP as long as the credential is valid.
Troubleshooting
Can't connect / authentication fails:
- Check whether the provider requires an app-specific password or OAuth2 rather than your regular account password
- Confirm you're using the correct port and encryption setting (143 with STARTTLS, or 993 for implicit TLS)
Folders/messages appear differently across devices:
- This shouldn't happen with proper IMAP sync — if it does, check for a client that's actually configured as POP3 rather than IMAP, or a sync/caching bug in a specific client app
Slow to load large mailboxes:
- Often a client-side indexing issue on first sync, especially with very large mailboxes — this is expected initial behavior for many clients rather than an IMAP protocol problem
"IMAP access is disabled" error:
- Many providers require IMAP to be explicitly enabled in account/security settings before any client can connect
Comparison / FAQ
| Port | Protocol | Key difference from 143 (IMAP) |
|---|---|---|
| 993 (IMAPS) | TCP | Same protocol, wrapped in implicit TLS from the start of the connection |
| 110 (POP3) | TCP | Downloads and typically removes messages from the server, rather than keeping a synchronized server-side mailbox |
| 25 (SMTP) | TCP | Handles sending mail; IMAP only handles retrieval and mailbox management |
Why does IMAP need port 993 if port 143 already works?
Port 143 is plaintext by default (with optional STARTTLS upgrade); port 993 provides implicit TLS from the very first byte of the connection, which is considered the more robust and unambiguous way to guarantee encryption.
Is IMAP better than POP3 for checking mail on multiple devices?
Yes — IMAP keeps your mailbox state synchronized on the server, so read status, folders, and messages look the same everywhere you check mail. POP3's download-and-delete model was designed around a single device.
Why do I need an app-specific password for IMAP with some providers?
Because IMAP's traditional authentication doesn't natively support two-factor authentication flows. Providers that require 2FA on the main account typically ask you to generate a separate app-specific password (or use OAuth2, where supported) specifically for IMAP clients.
Does deleting an email in my IMAP client delete it everywhere?
Yes, and this is expected — since IMAP treats the server as the single source of truth, actions like delete, move, and flag propagate to every device checking that mailbox, unlike POP3 where each client may have its own locally downloaded copy.