-
Notifications
You must be signed in to change notification settings - Fork 55
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
handle forwarded messages #11
Comments
When I want to forward, I just reply and change the recipient list. |
Yes, I think that would work, though in the long run it would be nice to have something more robust, I guess. |
My solution - rewrite org-msg-post-setup so that it includes the reply-to, and make sure the reply-to appears in the message even when forwarding - by changing mu4e~draft-forward-construct accordingly in mu4e-draft.el (though adding advice would have been a better solution)
|
Mail forwarding is not an easy feature to implement as it requires to modify the Mail User Agent. Also this is not a common use-case in my workflow and it is low priority. Michael-David Fiszer made some suggestion in Issue #11. This patch is the port of this suggestion. Signed-off-by: Michael-David Fiszer Signed-off-by: Jeremy Compostella <jeremy.compostella@gmail.com>
Hi Michael-David, I tried to take your suggestion of Regards, -Jeremy |
last in a whole bunch of reports (sorry!). I'm pretty sure that org-msg chokes on forwarded messages, because of this line:
which forwarded messages do not contain. Maybe there's a way to use
References
in an analogous way? Though that does seem somewhat more complex.The text was updated successfully, but these errors were encountered: