CMail OAuth2 Builds
These builds of CMail have preliminary support for OAuth2. These are pre-release builds and subject to change.
Currently, only native apps are supported. This functionality has been tested with GMail. Feedback from users would be appreciated to confirm if native apps are working with other providers (Microsoft services in particular) and co-operation with users will be necessary to implement and test other OAuth2 configurations such as Google Workspaces or Office 365 accounts where subscriptions are required. Please get in touch via the contact page if you are able to assist.
OAuth2 configuration within CMail is done via a built-in Web interface. This is activated using the -oauth2config option, along with a JSON-based data store location (specified using -oauth2db:filename). As CMail is portable and does not write anything to disk, there is no default OAuth2 database location, however, in order to run as a portable app, CMailGUI will use cmail_oauth2.json if this file exists in the same path as cmailgui.exe, consistent with how cmailgui.json is used currently.
|
Note
|
Unlike other protocols which rely on Bearer tokens to identify the account, OAUTHBEARER and XOAUTH2 authentication require an account name in addition to the token. The username configured in the Web interface must therefore match the username used to login. |
GMail
The following OAuth2 settings can be used for GMail accounts:
Username: <Your gmail.com e-mail address>
permission_url: https://accounts.google.com/o/oauth2/auth
token_url: https://oauth2.googleapis.com/token
scope: https://mail.google.com/
client-id and client-secret: Refer to https://developers.google.com/identity/oauth2/web/guides/get-google-api-clientid
Microsoft
TBD
Download
CMailOAuth2_20240626.zip CMail and CMailGUI 20240626 amd64 ONLY!