Repository navigation
0.4.0 (2026-11-03)
Summary
ImapKit Desktop can now test the OAuth sign-in of an email client. The new OAuth tab of the Server page turns on the OAuth 2.0 / OpenID Connect provider of ImapKit 5.3: a client signs in through the browser without a password and logs in to IMAP and SMTP with its tokens.
Who should upgrade
- Anyone testing an email client with Gmail or Microsoft 365 style OAuth sign-in: no real provider account is needed any more.
- Everyone else at their convenience: the only other change is a fix for a message preview that could stay empty when the app had just started.
Highlights
- An OAuth tab with the issuer (Copy, and Open for the provider's page in the browser), what a sign-in does (the consent page in the browser, always allow, always deny), the access token lifetime, and refresh tokens like Google.
- Clients in a table edited in place: the ImapKit test clients
imapkit,imapkit-approveandimapkit-denyto begin with, and your app's client ID with its own sign-in behavior and redirect URIs (loopback on any port when empty). - While the server runs: queue the outcome of the next sign-in (denied,
temporarily_unavailable,server_error, a wrongstateoriss, no redirect), and see the issued tokens with Expire Access Tokens and Revoke All to test refresh and re-authentication. - The XOAUTH2 and OAUTHBEARER extensions turn on with the provider, and the SMTP server takes AUTH XOAUTH2 with the same tokens.
- Every step of a sign-in is logged as the
oauthsession on the Connections page, and the Email client settings box lists the issuer and a client ID.
See ImapKit Desktop and the OAuth guide.
Features
- OAuth tab with the OAuth 2.0 / OpenID Connect provider of ImapKit (8d6c60d)
Bug Fixes
- keep a message given to the preview before WebView2 is ready (6fb6f64)