Moonchild wrote: ↑2025-07-10, 21:59
As I always say: Use the tools that work best for you.
I don't use Outlook, but have you, or anyone else, tried the procedure for Claws mail given in
https://www.claws-mail.org/faq/index.php/Oauth2#References?
It was revised in October 2024, after the Microsoft "lockdown", so I'm hoping it would work.
Also, as far as I've been able to determine, Claws mail, like Epyrus, is not a client registered with either Google or Microsoft.
Setting up OAuth 2.0 for Microsoft - for Outlook or Exchange
Step 1: Log in to Azure (Microsoft's cloud service)
- go to Microsoft Entra ID apps
- log in
- if a pop-up appears alerting you about access token issues, just click "ignore"; the pop-up will show up again in a few seconds, but in the meantime, you can continue with the procedure; after a certain number of clicks, the pop-up will stop
Step 2: Register Claws Mail as a new app
- click on "Add" > "App registration" (if the pop-up shows up, continue pressing "ignore")
- enter Name (e.g. "Claws Mail")
- set Supported account types to the most permissive option: "Accounts in any organizational directory and personal Microsoft accounts"
- set Redirect URI to "Public client/native"; for Claws Mail 4.2 and later, enter "http://127.0.0.1:8888" in the URL field
- click Register button (at the bottom)
Alternatively, if you leave the Redirect URI field empty, the interface will then reject the value "
http://127.0.0.1:8888". However, you can go to (left bar) "Manage" > "Manifest", look for "replyUrlsWithType" and replace it with the following:
"replyUrlsWithType": [ { "url": "
http://127.0.0.1:8888", "type": "InstalledClient" }, { "url": "
https://login.microsoftonline.com/commo ... tiveclient", "type": "InstalledClient" } ],
Step 3: Configure the app
...
), davmail works with microsoft and any kind of 2-factor auth, even when app password is not possible 
