Closed miversen33 closed 2 years ago
On successful login, there is a "Stay signed in?" dialog box that appears (yes/no question) and your audit log seems to say that it really needs an answer to this question.
I bet the least bad thing to do here is to forward the redirect URL to the client (and have them select OAuth2 as a method in their email client so that a popup opens on their side). It's still bad as it involves a GUI somewhere though...
We figured it out! There were several things that we needed to do, I have added them below
davmail.url
= https://outlook.office365.com/EWS/Exchange.asmx
davmail.mode
= O365Modern
Once all of that was done, we are now able to use davmail in headless mode with O365 tokens :)
I am not completely sure we needed to use the EWS
url but I dont want to make any further changes as we are quickly running out of time to deploy this (the O365 cutoff for POP3 is 10/01).
Thank you for the fantastic application :)
Hello!
I am researching if davmail is the appropriate tool for a niche usecase we have in environment, and I am running into an odd issue that I don't really know how to troubleshoot.
To explain the issue, I should give some context first.
We have a mail box that runs on outlook, which we have some scripts that reach out to and consume the inbox contents. It appears that microsoft is sunsetting traditional authentication methods in favor of oauth2 and so we are investigating ways to work around this. One of the routes we are looking into is using davmail as a sort of proxy (IE, we change our scripts to reach out to a deployed headless davmail instance instead of outlook).
That said, I am strugging to get davmail to properly authenticate a test user with
O365Modern
auth type on a headless server. It seems to be forcing the use of a redirect URL, except that as this is a headless server, that redirect URL will never be used.I have attached the log I am getting when I attempt to reach out (with domain, client id, and application id redacted)
My properties file is attached as well ( davmail.properties with domain specific details redacted)
I do have access to the audit details for our Azure instance, and I can see the error that was provided on the failed login
I dont really know where to go from here. I can provide whatever additional information is needed