Email Server LANMailServer

OAuth2 is currently supported by Microsoft Office 365/Exchange Online and Gmail. Other providers/applications that also support the OAuth2 standard can be configured independently, e.g., LANMailServer Email Server.

Difference Between BASIC/Standard Authentication and "Modern Authentication" OAuth2

The POP3, IMAP, and SMTP protocols provide authentication using a username/email address and password. Over the years, various simple and complex encryption methods have been developed to ensure that login credentials cannot be intercepted during client-server communication.
With "Modern Authentication" using OAuth2, permission from the user must be obtained via a browser using an additional app provided by the server operator. Once permission is granted, the application receives an access token. Authentication then occurs using this token without transmitting the password. The access token expires at short intervals, requiring a new one to be requested repeatedly. This is more secure than using the same password continuously.
Disadvantage of "Modern Authentication": A separate app must be created for each server operator, and proof of authenticity may be required, making this process time-consuming.

Information about OAuth: Wikipedia OAuth

Built-In OAuth2 App

An app is pre-integrated for accessing Microsoft accounts. You need to select the correct account type to gain access.

For Google accounts, you must create an app yourself due to the complex verification process: Create OAuth2 App in Google Cloud.

Newsletter SuperMailer: Import contacts from Microsoft Cloud or send emails via Microsoft Cloud.

This functionality uses a separate app with its own access tokens, which must be authorized separately.

Using OAuth2

In the respective dialog for sending or receiving emails, choose:

<SMTP/POP3/IMAP> AUTHentication Basic/Standard

OAuth2 <account type> or

OAuth2 <custom_app>.

You do not need to enter a password.

Then click on the "Test" button to authorize the app in the browser (authorization) and obtain an access token for the desktop program.

Using the Access Token

The desktop program will use the access token instead of the password in the future and will also update it automatically every 60 minutes. This access token will be used for the SMTP, POP3, and IMAP protocols for the respective email address when OAuth2 is selected for authentication.

Data Storage

The desktop programs SuperMailer, BirthdayMailer, FollowUpMailer, MailboxFetcher, and SuperSpamKiller Pro store the data encrypted in the Windows registry. All desktop programs access the same data, so it is not necessary to authorize access or create a new app in every desktop program.

The LANMailServer email server uses its own app and stores the data in the local database, allowing easy data transfer when moving the server.

Adding Custom OAuth2 Apps or Deleting Access Tokens

In the desktop program for configuring email sending or receiving, select "Manage OAuth2 Apps and Tokens."

See Also

OAuth2 App for Accessing Microsoft Accounts for SuperMailer, BirthdayMailer, FollowUpMailer, MailboxFetcher, and SuperSpamKiller Pro

OAuth2 App for Accessing Microsoft Accounts for LANMailServer

Create OAuth2 App in Microsoft Cloud for Office 365/Exchange Online

Create OAuth2 App in Google Cloud