thunderbird / thunderbird/thunderbird-android

Change reply behavior

Open
#3,738 30 comments 17 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

type: enhancement
Dominant language
Kotlin
Stars
14k
Forks
2.8k
Avg merge
3d 3h
Merged PRs (30d)
57

Description

Sometimes users seem to be surprised about the way K-9 Mail selects recipients when the "reply" action is used. I'm proposing to add more options with names that hopefully make it clearer which addresses will be selected as recipients.

Proposed behavior described via examples:
From: sender@example.org
To: you@example.org

Displayed actions (in order):

  • Reply (sender@example.org)

From: sender@example.org
To: unknown@example.org

Displayed actions (in order):

  • Reply (sender@example.org)
  • Reply to all (sender@example.org, unknown@example.org)

From: sender@example.org
To: you@example.org
Reply-To: other@example.org

Displayed actions (in order):

  • Reply (other@example.org)
  • Reply to all (sender@example.org, other@example.org)

From: sender@example.org
To: unknown@example.org
Reply-To: other@example.org

Displayed actions (in order):

  • Reply (other@example.org)
  • Reply to all (sender@example.org, other@example.org, unknown@example.org)

From: sender@example.org
To: you@example.org
List-Post: <mailto:list@example.org>

Displayed actions (in order):

  • Reply to list (list@example.org, sender@example.org)
  • Reply (sender@example.org)

From: sender@example.org
To: you@example.org
Reply-To: list@example.org
List-Post: <mailto:list@example.org>

Displayed actions (in order):

  • Reply to list (list@example.org, sender@example.org)
  • Reply (sender@example.org)

From: sender@example.org
To: you@example.org
Reply-To: other@example.org
List-Post: <mailto:list@example.org>

Displayed actions (in order):

  • Reply to list (list@example.org, other@example.org)
  • Reply (other@example.org)
  • Reply to all (sender@example.org, other@example.org, list@example.org)

From: sender@example.org
To: list@example.org
Reply-To: list@example.org
List-Post: <mailto:list@example.org>

Displayed actions (in order):

  • Reply to list (list@example.org, sender@example.org)
  • Reply (sender@example.org)

From: sender@example.org
To: list@example.org
Reply-To: other@example.org
List-Post: <mailto:list@example.org>

Displayed actions (in order):

  • Reply to list (list@example.org, other@example.org)
  • Reply (other@example.org)
  • Reply to all (sender@example.org, other@example.org, list@example.org)

From: sender@example.org
To: unknown@example.org
Reply-To: list@example.org
List-Post: <mailto:list@example.org>

Displayed actions (in order):

  • Reply to list (list@example.org, sender@example.org)
  • Reply (sender@example.org)
  • Reply to all (sender@example.org, list@example.org, unknown@example.org)

From: sender@example.org
To: unknown@example.org
Reply-To: other@example.org
List-Post: <mailto:list@example.org>

Displayed actions (in order):

  • Reply to list (list@example.org, other@example.org)
  • Reply (other@example.org)
  • Reply to all (sender@example.org, other@example.org, list@example.org, unknown@example.org)

Feedback is very welcome.


Update 1: Incorporated feedback from https://github.com/k9mail/k-9/issues/3738#issuecomment-440997017
Update 2: See https://github.com/k9mail/k-9/issues/3738#issuecomment-441495208

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

Start by reviewing the proposed recipient examples and the feedback linked in the issue comments. Trace the existing reply-action behavior in the Android app, then verify that the displayed actions and recipient lists match the documented cases.

Written by the indexing model from the issue text.

Assessment

Tech stack
kotlin
Domain
mobile
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.