I'm trying to use DavMail as a workaround to connect a hotmail/outlook.com/live.com email account to a Linux email client that doesn't, in itself, support OAuth, 2FA, etc.
Is it even appropriate for this use case? If it is, even if only experimentally, what settings are recommended that should theoretically work? Asking to try to separate whether there's something about my environment that's getting in the way, from not having it configured correctly in the first place.
Environment:
- Fedora 43 Workstation, default GNOME running an extension so I can see system tray icons if I want to (but see below)
- DavMail 6.6.0-4012, flatpak, from flathub
- Email address that started life as a hotmail address but now has an outlook.com address as its primary. 2FA enabled - I wouldn't have it any other way...
I'm aware of:
...which I imagined was the most up-to-date 'right way', but counterintuitively, I seemed to get further working around the OAuth version issues by modifying the redirect URL along these lines:
... but I didn't succeed, per se, in either case, so the latter could just be a red herring. At the end of the day, I don't know enough about this stuff to rule out this being a noob question.
Config: see attached properties file for config as of now, but, as per above, I've tried a number of other permutations previously.
davmail.properties.txt - .txt added for github's benefit.
Note, ports changed to 1144/1026 to deconflict it from an also-running protonmail bridge that's listening on the default ports, but I think that's neither here nor there.
Part of the issue is I don't understand the finer distinctions between the protocols. My instinct was O365Modern was the best match to what I was trying to do, but several articles pointed me to Interactive instead. On another occasion, I got as far as getting a code to enter into the dialog, but the client didn't seem to recognise I'd successfully logged in, and so on...
Putting all that aside and returning to the graph approach - davmail.enableGraph=true &
davmail.enableOidc=true & O365Modern (and using the account's normal password in the client) - here's what happened when I tried to set up the email account in the client:
- started DavMail with a no-tray override so I could see what was happening: flatpak run org.davmail.DavMail -notray
- hit 'create' on adding the outlook.com account to the client with email address and normal password
- no window of any kind appeared, but I was prompted to approve a sign-in (with a five-letter code) in MS Authenticator - fine, but nothing showed me the code to compare it to.
- approved sign-in anyway, passed biometrics, and everything seemed to proceed correctly on that side, however
- while I was doing that, both DavMail gateway and the email client more-or-less instantly (i.e. before I acted on the authenticaor notification) reported the login as failed (i.e. can't create the account).
Hopefully, that blow-by-blow is useful. Here's the log file (sans redacted personal info - hopefully I caught all):
davmail.log
Let me know if you need any other info. Happy to act as a 'crash test dummy' and try things out if this is a work in progress, and that would be helpful, but otherwise probably going to give up for now.
Appreciate the effort put into such tools, however. Thankless work, I imagine.
I'm trying to use DavMail as a workaround to connect a hotmail/outlook.com/live.com email account to a Linux email client that doesn't, in itself, support OAuth, 2FA, etc.
Is it even appropriate for this use case? If it is, even if only experimentally, what settings are recommended that should theoretically work? Asking to try to separate whether there's something about my environment that's getting in the way, from not having it configured correctly in the first place.
Environment:
I'm aware of:
...which I imagined was the most up-to-date 'right way', but counterintuitively, I seemed to get further working around the OAuth version issues by modifying the redirect URL along these lines:
... but I didn't succeed, per se, in either case, so the latter could just be a red herring. At the end of the day, I don't know enough about this stuff to rule out this being a noob question.
Config: see attached properties file for config as of now, but, as per above, I've tried a number of other permutations previously.
davmail.properties.txt - .txt added for github's benefit.
Note, ports changed to 1144/1026 to deconflict it from an also-running protonmail bridge that's listening on the default ports, but I think that's neither here nor there.
Part of the issue is I don't understand the finer distinctions between the protocols. My instinct was O365Modern was the best match to what I was trying to do, but several articles pointed me to Interactive instead. On another occasion, I got as far as getting a code to enter into the dialog, but the client didn't seem to recognise I'd successfully logged in, and so on...
Putting all that aside and returning to the graph approach - davmail.enableGraph=true &
davmail.enableOidc=true & O365Modern (and using the account's normal password in the client) - here's what happened when I tried to set up the email account in the client:
Hopefully, that blow-by-blow is useful. Here's the log file (sans redacted personal info - hopefully I caught all):
davmail.log
Let me know if you need any other info. Happy to act as a 'crash test dummy' and try things out if this is a work in progress, and that would be helpful, but otherwise probably going to give up for now.
Appreciate the effort put into such tools, however. Thankless work, I imagine.