Update: it turned out at the time of testing, my account was migrated, but my mailbox wasn't. That results in very unexpected Akonadi EWS behaviour.
Yesterday my mail was migrated and now I have succesful login + mail using Akonadi EWS + oAuth2!
Thx to whoever made this possible
Martin
On Mon, Jan 18, 2021 at 9:35 PM Paul Vixie <paul@xxxxxxxxxxx> wrote:
On Mon, Jan 18, 2021 at 04:35:40PM +0100, Myriam Schweingruber wrote:
> Forwarding this to a more specific mailing list
$dayjob uses EWS, and i was never able to get kmail to speak to that.
so, $dayjob had to enable the "imaps" and "smtps" service in ms-exchange,
and then i was able to read and send company e-mail via kmail. --vixie
re:
> ---------- Forwarded message ---------
> From: Martin van Es <mrvanes@xxxxxxxxx>
> Date: Fri, 15 Jan 2021 at 13:58
> Subject: O365 via EWS in kmail
> To: <kde@xxxxxxxxxxxx>
>
>
> Hi,
>
> The company I work for will migrate mail to O365 and we, the linux people
> are fighting to get this working in our favorite clients (davmail is
> mentioned a lot!). It seems kmail has an option to get this working:
>
> https://userbase.kde.org/Kmail/Configuring_Kmail/Accounts/Office_365
>
> But it doesn't work for me. I can authenticate using oAuth (I get an
> embedded browser popup) and the logs say I have a new token, but after that
> akonadi can't connect to the server (
> https://outlook.office365.com/ews/exchange.asmx). I'm still on Kubuntu
> 20.10, and I know that we're a bit behing kde framework and applications.
> Can this work on 20.10, or will this be fixed in 21.04 that comes with
> newer framework/applications?
>
> Grtz
> Martin
>
>
> --
> Pronouns: she/her
> Proud member of the Amarok and KDE Community:
> https://www.kde.org
> Protect your freedom and support the work of the FSFE:
> https://www.fsfe.org <http://www.fsfe.org/>
--
Paul Vixie
If 'but' was any useful, it would be a logic operator
