Mickaël Guessant

I double checked NTLM flags: latest version uses the same flags as DavMail v5 with HttpClient 3. Thus it may be that we have different values for username/domain/workstation. I added...

Ok so this looks like latest version. the domain does not seem right, are you sure it's a url? => please remove the davmail default domain setting It seems you...

Correct, mixed up order in RFC, fixed in trunk

Events must be very broken if you get a nullpointer there: means no VEVENT in content. Anyway I fixed the code to avoid this exception

I wasn"t aware of the https://outlook.office365.us endpoint so the default .com suffix is hardcoded for O365 in some places. => need to review code to make it compatible with non...

At least two urls are hardcoded: - login.microsoftonline.com - outlook.office365.com Can you confirm those would be the same but with .us suffix ?

@lhindir indeed this comment is related to GCC High (non .com), I refactored the code to regroup all reference to actual O365 urls in a single place (getO365LoginUrl) Of course...

@RickyDoug looks good, just please repost without the code= value, this is a sensitive token. It's probably expired by now, but we can't leave confidential tokens public

So do you have anything after check code ? We expect a request to https://login.microsoftonline.us Then Authenticated username: => would mean we obtained a token

With default DavMail clientid and redirecturi yes, with Microsoft native application clientId no, see https://github.com/mguessan/davmail/issues/273