Microsoft Outlook and Exchange are fixtures in most organizations. Calendars, shared mailboxes, meeting requests — the Exchange ecosystem handles a lot. But the email client itself, whether you’re using the classic desktop version or the newer Outlook for Windows, presents your inbox the same way it always has: a chronological list with folders on the left.

For people managing high volumes of email across multiple projects, that model doesn’t scale.

The IMAP Bridge

cji.email connects to your Microsoft Exchange or Microsoft 365 mailbox via IMAP, using OAuth2 for authentication. This is the same standard protocol Outlook uses when you access your work email on a mobile client. No special Microsoft account integration is required — if your Exchange server supports IMAP (which all modern hosted Microsoft 365 tenants do), cji.email can connect to it.

OAuth2 means you authenticate through Microsoft’s own login flow. cji.email never handles your password directly. After authorization, it receives an access token with limited scope, which it stores securely in the OS keychain. Your credentials stay in your control.

Turning Folders into Kanban Columns

Here’s the core idea: IMAP folders are just labels that group messages. Most Outlook users already have folders like “Action Required,” “Waiting,” “Projects,” and “Archive” — even if they don’t think of them in those terms.

cji.email reads those IMAP folders and maps them to Kanban columns. Each message becomes a card. Moving a card from one column to another moves the message to the corresponding IMAP folder — which syncs back to Exchange immediately. If you open Outlook on another device, the message is exactly where cji.email put it.

If you’re starting fresh, the Kanban columns cji.email recommends are:

  • Kanboard/Open — incoming messages that need triage
  • Kanboard/ToDo — messages that require a specific action from you
  • Kanboard/Waiting — messages where you’re waiting on someone else
  • Kanboard/Done — messages where the action is complete

These are just IMAP folders with names. Nothing proprietary. Nothing that locks you into cji.email.

Why Desktop-First Matters for Outlook Users

Many Outlook users work in environments with large mailboxes — years of archived messages, multiple shared mailboxes, distribution lists. Web-based clients and many IMAP clients struggle with this scale because they depend on server-round-trips for every operation.

cji.email’s Rust backend syncs messages locally using incremental IMAP IDLE. Once your mailbox is synced, loading a message, searching your archive, or filtering by sender happens locally. The Rust runtime handles large archives without the memory pressure that browser-based clients can suffer from.

For people on corporate networks where VPN latency makes every server call expensive, that local-first architecture makes a noticeable difference.

What Stays in Exchange

cji.email does not replace Exchange for everything. Meeting invitations, calendar management, shared mailboxes, and distribution list administration all remain in Exchange where they belong. cji.email is focused on one thing: making the email triage and action workflow faster and more visual.

If you need to respond to a meeting request, you’ll still do it through whatever calendar client you prefer. But by the time you get to that email in cji.email, you’ll have already moved it to the right column, you’ll know at a glance what’s waiting on you, and you won’t have lost it in an undifferentiated list of two hundred messages.

Getting Connected

Connecting cji.email to an Exchange or Microsoft 365 account takes about two minutes: add an account, choose Microsoft OAuth2 as the authentication method, and complete the Microsoft login flow. cji.email will discover your IMAP settings automatically for most Microsoft 365 tenants.

For on-premises Exchange environments with non-standard configurations, manual IMAP server and port settings are available in the advanced account settings.