On Fri, Aug 07, 2020 at 11:51:27AM +0200, Magnus Hagander wrote:
> On Fri, Aug 7, 2020 at 5:05 AM Noah Misch <noah@leadboat.com> wrote:
> > On Thu, Aug 06, 2020 at 11:37:17AM +0200, Magnus Hagander wrote:
> > > In this particular case, it was git-send-email setting
> > > content-transfer-encoding to 8bit and then passing utf8 data in there.
> >
> > What is wrong with that? It would be wrong to set
> > "Content-Transfer-Encoding:
> > BASE64" and then include utf8, but "Content-Transfer-Encoding: 8bit" sounds
> > okay under my limited understanding of MIME.
>
> You are of course correct. The content-transfer-encoding is fine. I was
> checking too many headers and forgot which one was actually the broken one.
>
> The problem is it does not specify the *charset*. It does so specifically
> for the From header, but not for the main body. And without an encoding
> specified, the main body is limited to 7 bit ascii (and it contained utf8
> which made things go boom).
Hmm. Can you reply attaching the verbatim message, or otherwise point to how
to view it? While I can cause an improper charset as follows, this doesn't
look like a match for the symptom you found.
$ echo ä >>README; git commit -m 'test utf8' README
[master 2cbac89] test utf8
1 file changed, 1 insertion(+)
$ git -c "sendemail.assume8bitEncoding=bogus" send-email --to=noah@leadboat.com HEAD^..HEAD
/tmp/UHeTvyTROO/0001-test-utf8.patch
(mbox) Adding cc: Noah Misch <noah@leadboat.com> from line 'From: Noah Misch <noah@leadboat.com>'
From: Noah Misch <noah@leadboat.com>
To: noah@leadboat.com
Subject: [PATCH] test utf8
Date: Sun, 9 Aug 2020 00:43:18 -0700
Message-Id: <1596958998-448745-1-git-send-email-noah@leadboat.com>
X-Mailer: git-send-email 1.8.3.1
MIME-Version: 1.0
Content-Type: text/plain; charset=bogus
Content-Transfer-Encoding: 8bit
...
