From: Glenn Morris <rgm@gnu.org>
To: Ken Olum <kdo@cosmos.phy.tufts.edu>
Cc: 26918@debbugs.gnu.org
Subject: bug#26918: 25.2; rmail edit corrupts mail if content-type header not displayed
Date: Thu, 08 Jun 2017 14:10:44 -0400 [thread overview]
Message-ID: <ebbmpyic4b.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <q52shjdyx32.fsf@cosmos.phy.tufts.edu> (Ken Olum's message of "Tue, 06 Jun 2017 11:06:41 -0400")
Ken Olum wrote:
> I'd be in favor of looking first at the edited message, and if there is
> no Content-Type header there, looking at the full headers of the
> original message. If Content-Type is ignored, but the user adds one in
> the edit buffer, I would replace the original one in the message with the
> new one supplied by the user. I think this is the general way that
> added headers are handled.
That sounds like the correct approach to me.
next prev parent reply other threads:[~2017-06-08 18:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-14 1:38 bug#26918: 25.2; rmail edit corrupts mail if content-type header not displayed Ken Olum
2017-06-05 21:16 ` Glenn Morris
2017-06-06 15:06 ` Ken Olum
2017-06-08 18:10 ` Glenn Morris [this message]
2017-06-19 18:40 ` bug#26918: rmail-cease-edit patches for bugs 26918 and 27353 Ken Olum
2017-09-08 9:11 ` bug#27353: " Eli Zaretskii
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=ebbmpyic4b.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=26918@debbugs.gnu.org \
--cc=kdo@cosmos.phy.tufts.edu \
/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).