From: David Bremner <david@tethera.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 34992@debbugs.gnu.org
Subject: bug#34992: 26.1; message-send-mail-with-mailclient mangles MIME messages
Date: Mon, 25 Mar 2019 13:09:30 -0300 [thread overview]
Message-ID: <87pnqfaqbp.fsf@tethera.net> (raw)
In-Reply-To: <83zhpjm06y.fsf@gnu.org>
Eli Zaretskii <eliz@gnu.org> writes:
>>
>> Notice that the whole encoded mime message is wrapped in a text/plain
>> part, which breaks most (all?) MUAs ability to read the message.
>>
>> I'm not sure what a sensible fix is here.
>
> One possibility would be for message-mode to refuse to add attachments
> when message-send-mail-function is set up to use the system mail
> client. The user should be told to attach using the mail client
> facilities instead.
That's a possibility, but something would have to be done for the other
code that programmatically adds attachments via mml tags. In addition to
debian-bug.el, a quick search suggests Gnus and mh-e (in emacs) and mu4e
and "Emacs Muse" (outside of emacs) are also vulnerable to this
problem. I would not be surprised if notmuch-emacs was as well, but I
didn't see it.
I guess the "interface" of send-mail-function and
message-send-mail-function is not very well defined, but it still feels
wrong to have radically different transport behaviour for different
choices. It almost seems like there should be a different customizable
variable(s) with different valid values for client code that needs more
guarantees.
next prev parent reply other threads:[~2019-03-25 16:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-25 12:43 bug#34992: 26.1; message-send-mail-with-mailclient mangles MIME messages David Bremner
2019-03-25 15:40 ` Eli Zaretskii
2019-03-25 16:09 ` David Bremner [this message]
2019-03-26 15:44 ` Richard Stallman
2019-03-26 16:49 ` Eli Zaretskii
2019-03-26 17:16 ` David Bremner
2019-05-13 19:58 ` Lars Ingebrigtsen
2019-06-22 7:42 ` David Bremner
2019-09-22 22:06 ` Lars Ingebrigtsen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87pnqfaqbp.fsf@tethera.net \
--to=david@tethera.net \
--cc=34992@debbugs.gnu.org \
--cc=eliz@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).