https://bugs.kde.org/show_bug.cgi?id=442180
--- Comment #3 from Jonas Andradas <j.andra...@gmail.com> --- Hi Iyán, thank you for your comments. I have tried changing this using qdbus as per your suggestions. I have managed to change both the oAuthAppId and oAuth2ReturnURI with qdbus org.freedesktop.Akonadi.Resource.akonadi_ews_resource_10 /Settings org.kde.Akonadi.Ews.Settings.oAuth2AppId "d3590ed6-52b3-4102-aeff-aad2292ab01c" qdbus org.freedesktop.Akonadi.Resource.akonadi_ews_resource_10 /Settings org.kde.Akonadi.Ews.Settings.setOAuth2ReturnUri urn:ietf:wg:oauth:2.0:oob These settings are changed fine, but when I try to authenticate, I am taken through the journey just as before, so still not able to use Kmail here :( When access is not allowed because the device is not "configured properly", this is what I get from EWS in the error: App name: App id: 00000000-0000-0000-0000-000000000000 IP address: <REDACTED> Device identifier: Not available Device platform: Android Device state: Unregistered So, despite setting the Custom UserAgent to Microsoft Office 2016, and the OAuth2 App id to Outlook's, it seems that, for some reason, these are not being properly sent to EWS, or at least not in the way the server expects them. -- You are receiving this mail because: You are watching all bug changes.
