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: > Yeah, same thing again, there was a corrupt message in the archive that > made it blow up. It's annoying that it just stops there and doesn't > actually produce an error :/
Confirmed that the whole month now downloads.
> 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).
