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: Set account by "to" field #4657

Closed
wants to merge 1 commit into from
Closed

Conversation

sorpaas
Copy link

@sorpaas sorpaas commented Jan 18, 2016

Currently, in multi-account mode, the mu4e layer guesses which account
to use to reply a message by its "maildir". However, some messages may
be forwarded and may need to use the original email address to reply.
This commit detects whether such an email address is defined in
"mu4e-account-alist", and uses that to do the replying if possible.

Currently, in multi-account mode, the mu4e layer guesses which account
to use to reply a message by its "maildir". However, some messages may
be forwarded and may need to use the original email address to reply.
This commit detects whether such an email address is defined in
"mu4e-account-alist", and uses that to do the replying if possible.
@sorpaas sorpaas changed the title Set account by "to" field in mu4e mu4e: Set account by "to" field in mu4e Jan 18, 2016
@sorpaas sorpaas changed the title mu4e: Set account by "to" field in mu4e mu4e: Set account by "to" field Jan 18, 2016
@syl20bnr
Copy link
Owner

Thank you 👍
I made some slight modifications in commit 92b2c4b
Cherry-picked into develop branch.

Note for next PRs: create a PR branch instead of using the develop branch, this way you won't be stuck if you want to do other modifications.

@syl20bnr
Copy link
Owner

Note sure why this PR has not been closed, but seems that it is already merged.

@syl20bnr syl20bnr closed this Jan 20, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants