thunderbird / thunderbird/thunderbird-android

Wrong identity chosen when replying from sent mail

Open
#6,895 1 comment 0 reactions 0 assignees View on GitHub

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 version

6.602

Where did you get the app from?

Google Play

Android version

13

Device model

No response

Steps to reproduce
  1. Use an account with multiple identities.
  2. Send an email to someone from an identity that is not the default.
  3. Find the email within the Sent mail folder.
  4. Select "Reply All" to send a follow-up email to the same recipients, from the same identity, or "Reply" to send a follow-up email to the same main recipient from the same identity.
Expected behavior

K9 should behave the same way it does when replying to an email from the inbox:

When replying from the sent folder, it should identify that the From address in the sent email being replied to matches one of the identities defined in the account, and select that as the From address in the composed reply.

When replying to emails from within the Inbox, it recognises that the To field matches an identity in the account and selects that as the From for the composed reply.

It seems this bug only exists when replying from the sent mail folder.

Actual behavior

K9 ignores/disregards the From field in the original email and instead always selects the From address to be the account initial/default identity, resulting in the email being composed and potentially sent from the wrong identity.

The bug is worse if you don't realise K9s error before you press send - assuming it will have chosen the from address correctly as it usually does, and so end up sending the email from the wrong identity, which has happened to me before.

By the way, this bug has been around for a while. I've only just got around to reporting it. I hope it can be given a high priority though. Hopefully it won't be too difficult to fix, given that it's a matter of replicating behaviour elsewhere for a special case.

Logs

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No source files or tests are named. Reproduce the issue on Android using an account with multiple identities, send from a non-default identity, then reply or reply-all from Sent; done means the composed reply selects the identity matching the original message's From address.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, kotlin
Domain
mobile
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.