https://bugs.kde.org/show_bug.cgi?id=500123
Arthur Kasimov <kodemeis...@outlook.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |kodemeis...@outlook.com
--- Comment #4 from Arthur Kasimov <kodemeis...@outlook.com> ---
I also ran into the same issue. Indeed, the OAuth2 access token expires after
several hours, but KMail never attempts to refresh it.
The workaround is to delete the access token in KWalletManager (mailtransports
-> Binary Data -> some_id). This forces a fresh authentication via the browser.
Unfortunately, this only works for several hours. After that you'll need to
reset the access token again.
kmailtransport triggers the token refresh only when ksmtp returns
KSmtp::LoginJob::TokenExpired error. In turn, ksmtp returns this error when the
server responds with a 334 reply containing a base64-encoded SASL challenge.
This works well with GMail but not with Outlook. I guess either kmailtransport
or ksmtp should be fixed to handle Outlook's specific behavior.
--
You are receiving this mail because:
You are watching all bug changes.
