thunderbird / thunderbird/thunderbird-android
Support different OAuth tokens for outgoing/incoming servers (e.g. Outlook with Microsoft Authenticator not working)
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 14k
- Forks
- 2.8k
- Avg merge
- 3d 3h
- Merged PRs (30d)
- 57
Description
Checklist
- I have used the search function to see if someone else has already submitted the same bug report.
- I will describe the problem with as much detail as possible.
App
K-9 Mail
App version
6.804
Where did you get the app from?
Google Play
Android version
LineageOS, Android 12
Device model
No response
Steps to reproduce
- Have an Outlook account with Microsoft Authenticator enabled
- Open K-9, go to settings, and tap "Add account"
- Go through account setup steps
Expected behavior
K-9 should be prompted twice for a password and Authenticator code: once for the incoming server settings, and once for the outgoing server settings. After entering the password twice, and passing the second Authenticator challenge, the server settings should be imported, and the account available in the app.
Actual behavior
K-9 is only prompted for the first password and Authenticator challenge. This causes it to not receive the outgoing server settings, which causes account enrollment in K-9 to fail.
Logs
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the account setup flow described in the reproduction steps and trace how incoming and outgoing server authentication are handled during Outlook enrollment. Reproduce the Microsoft Authenticator scenario, then verify that both server prompts and challenges are completed and the account is successfully imported.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kotlin
- Domain
- authentication, mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100