reply to sent e-mail

23 views
Skip to first unread message

Tamas Papp

unread,
Nov 11, 2024, 5:30:36 AM11/11/24
to mu-di...@googlegroups.com
Hi,

Previously if I replied to an e-mail I sent, it was addressed to the
addresse, now it is addressed to myself. This happened since I upgraded
to v1.12.7. Did something change since v1.10? I am using mu4e-context.

best

Tamas

Tassilo Horn

unread,
Nov 11, 2024, 6:08:59 AM11/11/24
to Tamas Papp, mu-di...@googlegroups.com
Tamas Papp <tkp...@gmail.com> writes:

Hi Tamas,

> Previously if I replied to an e-mail I sent, it was addressed to the
> addresse, now it is addressed to myself. This happened since I
> upgraded to v1.12.7. Did something change since v1.10?

Not sure but I don't have that issue. I think it's important that you
set message-alternative-emails and message-dont-reply-to-names to a list
of regexes that match all your email addresses. Those are skipped when
replying.

HTH,
Tassilo

Tamas Papp

unread,
Nov 11, 2024, 6:31:48 AM11/11/24
to Tassilo Horn, mu-di...@googlegroups.com
Hi Tassilo,

AFAIK my addresses should be set with

my init ----my-address=...

and within Emacs,

(mu4e-personal-addresses)

returns them correctly.

best

Tamas

Tassilo Horn

unread,
Nov 11, 2024, 6:51:29 AM11/11/24
to Tamas Papp, mu-di...@googlegroups.com
Tamas Papp <tkp...@gmail.com> writes:

> AFAIK my addresses should be set with
>
> my init ----my-address=...

That's true, too.

> and within Emacs,
>
> (mu4e-personal-addresses)
>
> returns them correctly.

Still the question remains if mu4e-compose-mode (being derived from
message-mode nowadays) handles mu4e-personal-addresses in addition to
the two message-mode customs I've mentioned and in such a way you
desire. You could try setting them to the value of
(mu4e-personal-addresses) in some early mu4e hook, e.g.,
mu4e-main-mode-hook and see if that helps.

Bye,
Tassilo

Tamas Papp

unread,
Nov 11, 2024, 8:37:33 AM11/11/24
to Tassilo Horn, mu-di...@googlegroups.com
On Mon, Nov 11 2024, Tassilo Horn wrote:

Neither works, I tried

(defun my-address-check (addr)
(cl-some (lambda (str) (string-match-p str addr)) (mu4e-personal-addresses)))

(setq message-alternative-emails 'my-address-check)
(setq message-dont-reply-to-names 'my-address-check)

However, in the meantime I found out by bisection that
mu4e-compose-dont-reply-to-self is now obsoleted. I tried

(setq message-dont-reply-to-names
'mu4e-personal-or-alternative-address-p)

instead which I think is the suggested replacement, but the issue still
persists.

However, if I use C-u (wide) before R then I get the expected behavior.

best

Tamas

Tassilo Horn

unread,
Nov 11, 2024, 9:04:14 AM11/11/24
to Tamas Papp, mu-di...@googlegroups.com
Tamas Papp <tkp...@gmail.com> writes:

Hi Tamas,

> However, if I use C-u (wide) before R then I get the expected
> behavior.

Ah, that's it! I myself always use wide-replies so that's the reason it
worked for me. I think recently something changed so that wide-replies
are now bound to W and R is just a normal reply (unless a prefix arg has
been given) which would actually reply to myself if the replied-to mail
has myself in From.

Bye,
Tassilo

Tamas Papp

unread,
Nov 11, 2024, 9:07:58 AM11/11/24
to Tassilo Horn, mu-di...@googlegroups.com
Re-reading the original 1.12 announcement, it is noted that “this only
works for wide replies”.

So I am wondering what the functional replacement is for

(setq mu4e-compose-dont-reply-to-self t)

is in 1.12, ie behave as if all replies were “wide” _automatically_ when
they contain my own addresses?

best

Tamas

Nikos Patikas

unread,
Nov 11, 2024, 9:37:04 AM11/11/24
to Tamas Papp, Tassilo Horn, mu-di...@googlegroups.com

Hi Tamas,

version 1.12 broke this functionality for me and the email reply in a
straightforward dwim way it used to be.

To avoid replying to your addresses I have set this:

(setq message-dont-reply-to-names #'mu4e-personal-or-alternative-address-p)

Source:

https://www.djcbsoftware.nl/code/mu//mu4e/Other-settings.html

To get wide replies only assign the "R" to the #'mu4e-compose-wide-reply


To get similar reply functionality with 1.10 I have this:

(define-key mu4e-compose-minor-mode-map "R" 'mu4e-reply-menu-hydra/body)

(defhydra mu4e-reply-menu-hydra (:color pink :hint nil)
"Reply Menu:"
("c" nil "cancel")
("a" #'mu4e-compose-wide-reply "Reply to all" :color blue)
("s" #'mu4e-compose-reply "Reply to sender" :color blue)
)


Best,
Nikos
--
Nikos Patikas

Joost Kremers

unread,
Nov 11, 2024, 10:34:30 AM11/11/24
to Nikos Patikas, Tamas Papp, mu-di...@googlegroups.com, Tassilo Horn
On Mon, Nov 11 2024, Nikos Patikas wrote:
> To get similar reply functionality with 1.10 I have this:
>
> (define-key mu4e-compose-minor-mode-map "R" 'mu4e-reply-menu-hydra/body)
>
> (defhydra mu4e-reply-menu-hydra (:color pink :hint nil)
> "Reply Menu:"
> ("c" nil "cancel")
> ("a" #'mu4e-compose-wide-reply "Reply to all" :color blue)
> ("s" #'mu4e-compose-reply "Reply to sender" :color blue)
> )

Yes, I did something similar, though without hydra:

```

(defun jk/compose-mode-maybe-wide-reply ()
"Reply to a message, asking whether it should be a wide reply or not."
(interactive)
(mu4e-compose-reply (y-or-n-p "Reply to all? ")))
```

Then bind that function to R in `mu4e-compose-minor-mode-map`:

```
(use-package mu4e
...
:bind
...
:map mu4e-compose-minor-mode-map
("R" . jk/compose-mode-maybe-wide-reply))
```

Though this way you're always asked, instead of only when there's reason
to (i.e., when the original message had multiple recipients).

--
Joost Kremers
Life has its moments

Tassilo Horn

unread,
Nov 12, 2024, 12:36:33 AM11/12/24
to Joost Kremers, Nikos Patikas, Tamas Papp, mu-di...@googlegroups.com
Joost Kremers <joostk...@fastmail.fm> writes:

>> (define-key mu4e-compose-minor-mode-map "R" 'mu4e-reply-menu-hydra/body)
>>
>> (defhydra mu4e-reply-menu-hydra (:color pink :hint nil)
>> "Reply Menu:"
>> ("c" nil "cancel")
>> ("a" #'mu4e-compose-wide-reply "Reply to all" :color blue)
>> ("s" #'mu4e-compose-reply "Reply to sender" :color blue)
>> )
>
> Yes, I did something similar, though without hydra:
>
> ```
>
> (defun jk/compose-mode-maybe-wide-reply ()
> "Reply to a message, asking whether it should be a wide reply or not."
> (interactive)
> (mu4e-compose-reply (y-or-n-p "Reply to all? ")))
> ```
>
> Then bind that function to R in `mu4e-compose-minor-mode-map`:

My version is this:

--8<---------------cut here---------------start------------->8---
;; I keep on sending replies (R) instead of wide replies (W), so better make
;; R ask if I'm really sure.
(defun th/mu4e-compose-reply-filter-args (args)
"Ask if we actually want a wide reply (Reply All)."
(list (or (car args) ;; the first arg is `wide'.
(yes-or-no-p "Wide reply? "))))
(advice-add #'mu4e-compose-reply
:filter-args
#'th/mu4e-compose-reply-filter-args)
--8<---------------cut here---------------end--------------->8---

So when I hit R, it'll query if I actually want a wide reply each time.

Bye,
Tassilo

Dirk-Jan C. Binnema

unread,
Nov 12, 2024, 2:20:22 AM11/12/24
to mu-di...@googlegroups.com
For this, M-x mu4e-compose-supersede may be useful.

Anyway, _many_ things changed in composing messages in 1.12.x because
mu4e now re-uses the Gnus machinery for that. This fixed bugs and brings
new functionality, and overall lessens maintenance. As much as we tried,
old-mu4e behaviors changed in a few cases... time is limited.

Kind regards,
Dirk.

--
Dirk-Jan C. Binnema Helsinki, Finland
e:dj...@djcbsoftware.nl w:www.djcbsoftware.nl
gpg: 6987 9CED 1745 9375 0F14 DA98 11DD FEA9 DCC4 A036

Tamas Papp

unread,
Nov 12, 2024, 5:01:35 AM11/12/24
to mu-di...@googlegroups.com
On Tue, Nov 12 2024, Dirk-Jan C. Binnema wrote:

> On Monday Nov 11 2024, Tamas Papp wrote:
>
>> Hi,
>>
>> Previously if I replied to an e-mail I sent, it was addressed to the
>> addresse, now it is addressed to myself. This happened since I upgraded
>> to v1.12.7. Did something change since v1.10? I am using mu4e-context.
>
> For this, M-x mu4e-compose-supersede may be useful.
>
> Anyway, _many_ things changed in composing messages in 1.12.x because
> mu4e now re-uses the Gnus machinery for that. This fixed bugs and brings
> new functionality, and overall lessens maintenance. As much as we tried,
> old-mu4e behaviors changed in a few cases... time is limited.

No worries, I can live with the new setup, I was just wasn't aware of
the wide reply option. Just need to retrain muscle memory to press W,
or bind mu4e-compose-superseed to a key.

thanks for maintaining mu4e!

best

Tamas
Reply all
Reply to author
Forward
0 new messages