unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Rainer Gemulla" <rgemulla@gmx.de>
To: 38654@debbugs.gnu.org
Subject: bug#38654: Further details
Date: Fri, 10 Jan 2020 14:04:29 +0000	[thread overview]
Message-ID: <emd170fab9-1fa2-4b9e-ae38-50e97b314aa8@macho> (raw)
In-Reply-To: <emb0fe1189-106a-4f38-b16c-186faddf7065@potestas>


[-- Attachment #1.1: Type: text/plain, Size: 1692 bytes --]

The consequence of this bug is that Emacs sends incorrect messages 
without the sender noticing. When such a message is opened by the 
recipient (in any other email client I tried, including in Emacs), the 
content is not readable. This is an major bug.

The bug happens (mostly?) when a message is forwarded: the new parts 
added by the sender are lost because they are incorrectly encoded. The 
correct encoding and the incorrect one obtained in Emacs 27 below. The 
problematic parts are marked in red.

BEGIN CORRECT RESULT
From: a <at> b.ce
To: c <at> d.de
Subject: Test
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="=-=-="
--text follows this line--
--=-=-=
Content-Type: text/plain

Test


--=-=-=
Content-Type: message/rfc822
Content-Disposition: inline

--====-=-=
Content-Disposition: inline
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="====-=-="

Some text.

--====-=-=
Content-Type: text/html; charset=utf-8

Some more text.

--====-=-=--

--=-=-=--
END CORRECT RESULT
BEGIN INCORRECT RESULT AFTER STEP 9
From: a <at> b.ce
To: c <at> d.de
Subject: Test
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="=-=-="
--text follows this line--
--=-=-=
Content-Type: multipart/alternative; boundary="====-=-="
Content-Transfer-Encoding: base64

VGV4dAoK
--=-=-=
Content-Type: message/rfc822
Content-Disposition: inline

--====-=-=
Content-Disposition: inline
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="====-=-="

Some text.

--====-=-=
Content-Type: text/html; charset=utf-8

Some more text.

--====-=-=--

--=-=-=--
END INCORRECT RESULT AFTER STEP 9

[-- Attachment #1.2: Type: text/html, Size: 2703 bytes --]

[-- Attachment #2: Type: application/pgp-signature, Size: 876 bytes --]

  reply	other threads:[~2020-01-10 14:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-17 21:16 bug#38654: 27.0.50; mml-to-mime may produce faulty email messages Rainer Gemulla
2020-01-10 14:04 ` Rainer Gemulla [this message]
2020-03-03 15:12 ` Rainer Gemulla

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=emd170fab9-1fa2-4b9e-ae38-50e97b314aa8@macho \
    --to=rgemulla@gmx.de \
    --cc=38654@debbugs.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).