-
Notifications
You must be signed in to change notification settings - Fork 61
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
inline images in parent message have the wrong content-disposition (attached) when replying #177
Comments
molok
changed the title
inline images in parent message became have the wrong content-disposition (attached) when replying
inline images in parent message have the wrong content-disposition (attached) when replying
Jan 9, 2024
jeremy-compostella
added a commit
that referenced
this issue
Jan 16, 2024
This addresses Issue #177. Signed-off-by: Jeremy Compostella <[email protected]>
jeremy-compostella
added a commit
that referenced
this issue
Jan 16, 2024
This addresses Issue #177. Signed-off-by: Jeremy Compostella <[email protected]>
Is #178 working for you ? |
jeremy-compostella
added a commit
that referenced
this issue
Jan 16, 2024
This addresses Issue #177. Signed-off-by: Jeremy Compostella <[email protected]>
jeremy-compostella
added a commit
that referenced
this issue
Mar 19, 2024
This addresses Issue #177. Signed-off-by: Jeremy Compostella <[email protected]>
peterhoeg
pushed a commit
to peterhoeg/org-msg
that referenced
this issue
Apr 19, 2024
This addresses Issue jeremy-compostella#177. Signed-off-by: Jeremy Compostella <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I receive a lot of emails with inline images (usually in the signature), when replying an email with inline images I've noticed that the MIME message generated by org-msg sets Content-Disposition as "attached" instead of "inline", this looks weird in clients like Outlook Web.
the only workaround I've found so far is to set
this way
mml
forces content-disposition inline for attachments with paths matching the ".*tmp.*cid.*image.*png"" regex, which matches whereorg-msg
stores that kind of attachments on my machine.I'm sure there are lots of way this can break, but at least it I won't spam my colleagues with "fake" attachments.
I'm using the latest org-msg, mu4e 1.10.8 and Emacs 29.1
The text was updated successfully, but these errors were encountered: