OAuth2 documentation inconsistency

[zerszenyi]

Hello,

I find that the instructions in the documentation don't match the options presented in the application.

Specifically, when I try to add a new OAuth2 token configuration, my options are as follows:

• Google Mail (Authorization code flow)

• Microsoft Exchange Online (Authorization code flow)

• Microsoft Exchange Online (Client credentials flow)

The options presented in the documentation at https://www.znuny.org/en/blog/modern-au ... -microsoft are:

• Google Mail

• Microsoft Outlook (common)

• Microsoft Outlook (consumers)

• Microsoft Outlook (organizations)

The document stops short at explaining which Microsoft Outlook option should be used where and how they map to what actually is presented in the application interface.

It also doesn't mention whether the mailbox should be a fully licensed user mailbox or can it be a shared mailbox. If shared mailbox, do I need Send As permissions, or Full Control is sufficient as explained in the tutorial at https://www.youtube.com/watch?v=I-ngN8Ep9VM?

It does is failing more times than it works, and from other posts I can see that I am not alone in this jungle of inconsistencies and incomplete information.

While it is an awesome piece of software, if it can't send and receive email using one of the world's most popular mail system, it is useless like windshield wipers on a submarine.

I would appreciate very much a comprehensive list of prerequisites and scenarios that actually work and it is stable, and an errata to the documentation adapted to the actual application interface.

Thank you.