Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[mu4e bug] Reply to sender (only) does not work #2535

Closed
3 tasks done
Chris00 opened this issue Aug 16, 2023 · 0 comments · Fixed by #2536
Closed
3 tasks done

[mu4e bug] Reply to sender (only) does not work #2535

Chris00 opened this issue Aug 16, 2023 · 0 comments · Fixed by #2536
Labels
bug mu4e specific for mu4e new

Comments

@Chris00
Copy link
Contributor

Chris00 commented Aug 16, 2023

Describe the bug & How to Reproduce

Reply to any message with “reply to sender only” and all addresses end up in To.

In the function

(defun mu4e~draft-create-to-lst (origmsg)
  "Create a list of address for the To: in a new message.
This is based on the original message ORIGMSG. If the Reply-To
address is set, use that, otherwise use the From address. Note,
whatever was in the To: field before, goes to the Cc:-list (if
we're doing a reply-to-all). Special case: if we were the sender
of the original, we simple copy the list form the original."
  (let* ((reply-to
         (append
          (plist-get origmsg :to)
          (or (plist-get origmsg :reply-to) (plist-get origmsg :from))))
         (reply-to (cl-delete-duplicates reply-to
                                         :test #'mu4e~draft-address-cell-equal)))
    (if mu4e-compose-dont-reply-to-self
        (cl-delete-if
         (lambda (to-cell)
           (mu4e-personal-address-p (mu4e-contact-email to-cell)))
         reply-to)
      reply-to)))

I do not understand the (plist-get origmsg :to) because it will put all addresses in To regardless of whether one wants to replay to all or not.

Environment
Debian,
mu commit 6168d77

Checklist

  • you are running either an 1.8.x/1.10.x release or master (otherwise please upgrade)
  • you can reproduce the problem without 3rd party extensions (including Doom/Evil, various extensions etc.)
  • you have read all of the above
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug mu4e specific for mu4e new
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant