[GH-ISSUE #160] reply-all should reply to all irrespective of whether reply-to is set #120

Closed
opened 2026-03-03 01:19:57 +03:00 by kerem · 0 comments
Owner

Originally created by @d99kris on GitHub (May 18, 2024).
Original GitHub issue: https://github.com/d99kris/nmail/issues/160

Originally assigned to: @d99kris on GitHub.

Description:
When performing Reply All (i.e. shortcut r) and the email being replied to has a Reply-To: header, the desired behavior should be to reply to all, and only use the Reply-To: value in place of the From: value, i.e. for the To: field in the response email being composed.

For regular Reply (i.e. shortcut R) no change is needed, it already replies using the Reply-To: address if set, otherwise using From: value for the To: field in the response email.

The above desired behavior is based on Gmail as of today (2024 May 18) and Alpine v2.26.

How to reproduce it:

Perform Reply All on an email with a Reply-To: header, for example a Github notification email.

Environment:

  • Version: v4.62 (or earlier)
  • OS / distro: Any (tested on macOS)
Originally created by @d99kris on GitHub (May 18, 2024). Original GitHub issue: https://github.com/d99kris/nmail/issues/160 Originally assigned to: @d99kris on GitHub. **Description**: When performing `Reply All` (i.e. shortcut `r`) and the email being replied to has a `Reply-To:` header, the desired behavior should be to reply to all, and only use the `Reply-To:` value in place of the `From:` value, i.e. for the `To:` field in the response email being composed. For regular `Reply` (i.e. shortcut `R`) no change is needed, it already replies using the `Reply-To:` address if set, otherwise using `From:` value for the `To:` field in the response email. The above desired behavior is based on `Gmail` as of today (2024 May 18) and `Alpine` v2.26. **How to reproduce it**: Perform `Reply All` on an email with a `Reply-To:` header, for example a Github notification email. **Environment**: - Version: v4.62 (or earlier) - OS / distro: Any (tested on macOS)
kerem 2026-03-03 01:19:57 +03:00
  • closed this issue
  • added the
    bug
    label
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/nmail#120
No description provided.