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 composer no longer picks the right email address from where to send messages or reply to them #2708

Closed
Adocentyn opened this issue May 16, 2024 · 1 comment
Labels
bug mu4e specific for mu4e new

Comments

@Adocentyn
Copy link
Contributor

Describe the bug

Give the bug a good title.
Since the 1.12.5 it is no longer possible for a setup using several email accounts and no contexts to choose which email with which to compose messages and it is no longer possible to reply to emails using the email address that the message was sent to.

How to Reproduce

WIth mu/mu4e 1.12.5, have a setup with several email accounts and the ability to have each email account available as a potential sender - plus the rule that replying to an email is done by default with from the account the message was sent to.

Try to compose an email and try to reply from an existing email.

** Results **
mu4e has picked the first email account in the init file and treats it as the default and sole sender of emails even when replying to messages in other inboxes.

Environment

ArchLinux
Emacs 29.3
mu4e 1.12.5

@Adocentyn Adocentyn added bug mu4e specific for mu4e new labels May 16, 2024
@djcb
Copy link
Owner

djcb commented May 17, 2024

I'd recommend using contexts, but it should work without. I think we were missing a call to mu4e-compose-pre-hook, which I have added.

The gnus-based composer depends on message-alternative-emails to decide if it should use the To: address as a From: for replies; but I suppose mu4e could try to set that for you.

I'll push some changes.

@djcb djcb closed this as completed in a9495f7 May 17, 2024
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

No branches or pull requests

2 participants