question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Change reply behavior

See original GitHub issue

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

Issue Analytics

  • State:open
  • Created 5 years ago
  • Reactions:12
  • Comments:16 (8 by maintainers)

github_iconTop GitHub Comments

3reactions
neiljerramcommented, Jun 7, 2019

Is this change going to actually happen soon? After an accidental and semi-embarrassing reply-to-list today - again - I’ve ended up here, and it’s clear that many k9 users have been burned by this, not just me.

Could we at least have an option - soon - to ignore List-Post?

(In my view List-Post should have nothing to do with replying. It tells you how to write a new message to the list.)

3reactions
nomiscommented, Dec 9, 2018

I think it’s customary for list replies to reply to both list and sender. It’s rarely harmful at least, and removing recipients from the list is easier than adding more. That way we can get rid of an entire option, since “reply to list” and “reply to all” become the same for typical list messages.

Please don’t do this, “reply to list” should be a separate option and only reply to the list. I’m fed up of people sending me duplicate messages to different folders by copying me in mailing list replies.

Read more comments on GitHub >

github_iconTop Results From Across the Web

How to Change the Default Reply Action Gmail Setting
Sign in to Gmail. Click the gear icon. Choose See all settings. Select your preferred Default reply behavior. Click Save changes.
Read more >
Gmail: How to Set the Default Reply Behavior - Technipages
Set default reply options​​ Click on the cogwheel icon, then click “See all settings”. In the “General” tab of the settings, find the...
Read more >
Gmail: Default Reply Behavior - Teacher Tech with Alice Keeler
In Gmail you can now set your preferred default for emails. Click on the settings cog and choose “Settings.” On the General settings...
Read more >
GMAIL: Default Reply Behavior - YouTube
Set your Default Reply Behavior to " REPLY " not " REPLY ALL"! ... How to Change Wordpress Admin Email Without Confirmation |...
Read more >
Reply settings in Outlook on the web - Microsoft Support
At the top of the page, select Settings Settings > View all Outlook settings. Select Mail > Compose and reply. Under Reply or...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found