Why IMAP (and CalDAV) still matter

Every few years someone announces that IMAP is finished. The web client is good enough; the mobile app is good enough; proprietary sync will cover the rest. Then an agency connects a helpdesk, a consultant opens Thunderbird, a phone needs contacts from somewhere other than a single vendor’s cloud, and the old protocols quietly get another lease of life.

This is not nostalgia. It is about what happens when email is infrastructure rather than a destination website.

What IMAP actually buys you

IMAP is a way for a mail client to talk to a mailbox on a server while leaving the mail on the server. Folders stay in sync. Flags stay in sync. Several devices can share one mailbox without the “which copy is real?” mess that POP3 encouraged when people downloaded and deleted from the server by default.

The important part for ops is not the history lesson. It is that IMAP is a contract. Anything that speaks IMAP can work with anything that offers IMAP: desktop clients, mobile clients, backup tools, ticketing systems that read a support inbox, scripts that file mail into the right place. You are not waiting for your mail host to build a one-off integration for each tool in your stack.

When a host treats IMAP as optional, or rate-limits it into uselessness, or hides it behind an expensive bridge, they are telling you the web app is the product and the mailbox is a captive audience. That can be acceptable for personal use. It is a poor fit for teams that already have clients and systems they trust.

POP3 still has a narrow job

POP3 is simpler and rougher. It was designed around “download this mail to this machine”. Most people should prefer IMAP for day-to-day use. POP3 still appears in older devices, some appliances, and workflows that deliberately pull mail into a single archive host. Keeping POP3 available costs a competent host little and avoids stranding those edge cases. Turning it off for fashion reasons rarely helps the people who still need it.

Calendars and contacts are part of the same story

Mail is only one of the three things people mean when they say “my email account”. Calendars and address books travel with it. CalDAV and CardDAV are the boring, useful standards for syncing those over the network. Like IMAP, they let you choose clients: a phone’s built-in calendar, a desktop app, a shared team calendar workflow that does not require everyone to live inside one web UI.

If calendars and contacts only sync through a proprietary mobile app, changing phone vendors — or mixing Android and iPhone in one team — becomes a migration project. Standards sync makes that a configuration task instead.

ActiveSync and the mobile middle ground

Many organisations also use ActiveSync (the protocol family behind a lot of “Exchange-style” mobile setups) to push mail, calendars and contacts to phones. That can be an excellent daily driver on mobile even when desktop access stays on IMAP and CalDAV. The point is not to pick a religion. The point is to avoid a host that only offers a polished browser window and shrugs at everything else.

A practical setup for a small agency often looks like this: IMAP for desktops and for systems that must read a mailbox; CalDAV/CardDAV for calendars and contacts across devices; ActiveSync where phones benefit from it; webmail when you are on someone else’s computer. None of that requires abandoning the web client. It requires the web client not to be a dead end.

Web-only lock-in fails in predictable ways

The failure modes are familiar:

• A ticketing product wants an IMAP inbox for support@yourdomain and cannot use your webmail UI.
• Someone needs offline access on a laptop without inventing a new workflow.
• You want a second opinion client because the official app had a bad week.
• You are migrating hosts and need to export or dual-run without rewriting every integration.
• A contractor must be given access to one folder without handing them the keys to an entire consumer identity ecosystem.

Each of these is easier when the mailbox speaks ordinary protocols. Each of them becomes a support ticket pile when it does not.

What to check before you commit to a host

Ask dull questions and keep the answers:

• Is IMAP available on all plans you would actually buy, or only on a premium tier?
• Is POP3 still offered if you need it?
• Are CalDAV and CardDAV documented, with working examples?
• Is there a sane mobile path (ActiveSync or well-behaved IMAP push), and what are the limits?
• Can you use application-specific passwords with 2FA without theatre?

If the sales page talks only about “beautiful webmail” and never mentions the protocols your other tools speak, believe that omission.

Standards are how small teams stay portable

Large consumer mail products can afford to invent their own world. Small teams usually cannot. Portability — the ability to point a client at a different server, or to keep a helpdesk integration when you change host — is a form of operational safety. IMAP, CalDAV and CardDAV are not exciting. They are how you avoid betting the whole communications stack on a single vendor’s roadmap.

Redmail has been running hosted email since 1997, with advanced webmail plus IMAP and POP3 as standard, calendars and contacts sync, and mobile options including ActiveSync on plans that include it. If you want a mailbox that still plugs into the rest of your tools, you can create an account or see what is included.