Does K9Mail support Microsoft's modern authentication methods

I have received an email advising that effective Sep 16, 2024, "Microsoft will no longer support the use of third-party email and calendar apps which ask you to sign in with only your Microsoft Account username and password. To keep you safe you will need to use a mail or calendar app which supports Microsoft’s modern authentication methods. "

Does K9Mail support these new methods, and if so, how do I set up using them? Or is this the end for K9Mail on the outlook.com domain?

Rob

The search would have answered that question, cketti even made a nice guide for Outlook + OAuth 2.0 right here :wink:

1 Like

Thanks for that. Sorry, I thought I had searched but must have missed it.

1 Like

Sorry for reopening this thread but I am in the same situation and I’m having a hard time making it work. I’m using k9 mail v6.711 on Android and I’m following the tutorial linked to this thread. While I can login to my account and give the rights to k9 mail to access my emails, when I click on continue nothing happen. I remain stuck on a white screen and it does not proceed any further.

I deleted my account and tried to reinstall it from scratch but no luck so far

I trier using different web browsers as default, removing all tracking protection during the procedure but no progres so far. For the record I tried with the following browsers:
Firefox
Edge
Duckduckgo

I cannot install chrome as I am on e.os which does not support chrome browser.

Any help about this would be greatly appreciated.

Below a screenshot of the screen on which I’m stuck. Clicking on continue does not do anything.

OK problem solved: the issue is not coming from k9 mail but from the custom build of k9 mail they made on eOS… Another limitation from this os I guess. Downloading k9 mail from the app lounge solved my issue. Hope this info will help anyone using similar configuration.

I’m trying to follow that guide, but I’m stuck at step 5. After tapping “next”, it tries to open “microsoftonline.com”, which doesn’t exist, so I get an “address not found” error and can’t continue. Can’t I just indicate the right address somewhere so I can go on with the process?

i believe that you should be being directed to “login.microsoftonline.com”, rather than simply “microsoftonline.com”. i’m not certain where/why that incorrect redirect is coming from. does the interface at that point let you add the “login.” part?

I’m afraid not. I wonder what’s causing the bad redirection. Is it the K-9 app, or the Microsoft server itself? Either way, I’d say we should be seeing quite a few similar cases.

So… no tips on this bad redirection issue? Sorry to insist, but we’re on a bit of a ticking clock situation here. I’d hate to be forced to switch to another client just to be able to use that one account, K-9 has worked so well for me until now, and it’s not like this is even K-9’s fault.

Maybe also sent debug log here. This might give some insight on what is going on

Right, so I toggled extra debug info, tried to change authentication to OAuth2.0, failed as usual, then exported the debug file. I’m not familiar with that kind of file. Is there any part of it that would be particularly interesting? Is there something I’d be better off redacting before just pasting it whole?

According to LoggingErrors · thunderbird/thunderbird-android Wiki · GitHub I guess you should check for passwords in this file only and remove them if available. Other than that the full log should be provided here or maybe even better in Github

O.K., so I pasted the log at --------- beginning of system08-05 09:58:58.427 8056 8056 D ActivityThread: - Pastebin.com, since I didn’t figure out how to post it here. I’m afraid I don’t have a GitHub account, but if anyone thinks this log could help and would like to upload it themselves, feel free. And thanks.

Mhhh… do not see anything relevant (but Im am no K9 dev). Maybe someone else?

Well, thanks anyway for trying. I’m still surprised no one else seems to have encountered this, though. I’m assuming the “e-mail of impending doom” was sent to anyone that wasn’t using OAuth2.0. Are you guys stuck like me? Or did you actually manage to just make the transition to OAuth2.0 following the guide above without encountering the bad redirection?

So I managed to sort this out and it’s the weirdest thing, but I’m posting it here in case it helps anyone still struggling with this. Looking at the guide above, I focused on point 5 (“If your browser is not already logged in to your Microsoft account, you will be asked to log in.”). So I thought “hey, why don’t I just log in from my browser?”. Tried to, but whenever I hit “sign in”, I’d keep getting that “address not found” error, even from the browser, even hitting a “sign in” link on an official Microsoft site. So I remembered I’d had trouble logging in to my Microsoft account before and thought of something: how about I disable wi-fi access and try logging in with my cell phone data instead? Tried that, worked without a hitch. I can’t for the life of me figure out what the problem with my wi-fi connection and Microsoft’s log-in servers could be, but at least I can keep using K-9 now. So I got that going for me. Which is nice.

2 Likes

Is there also a solution when I want to use pop3 instead of imap?

No, and POP3 is a very bad idea when using K-9. You will regret choosing POP3 when you get a new phone. Because K-9 does not support exporting the messages, you will likely lose some of your email then. There is no reason to stick to POP3 nowadays, and I hope that support for POP3 soon gets removed to avoid all kinds of trouble.

(for example, attachment handling is super hacky in POP3 because the protocol does not support them natively)

1 Like

Mr. Asdfghjkl.
Nice to meet you.
If you disconnected the Wi-Fi and the mobile network solved the problem, it is actually possible that the security level of the Wi-Fi router’s firewall is too high, or that the VPN is also related to the problem, which makes it impossible to log in. If you have to set it up again, try lowering or stopping the security level of the Wi-Fi firewall or disconnecting the VPN.

1 Like

Another possibility - ensure you are not using a secondary account alias as your username: