[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Nmh-workers] RFC 2047 vs RFC 2231 encoding for MIME parameters

From: Ralph Corderoy
Subject: Re: [Nmh-workers] RFC 2047 vs RFC 2231 encoding for MIME parameters
Date: Wed, 28 Sep 2016 19:10:36 +0100

Hi Ken,

> RFC 2047 encoding is ALSO used when you attach a filename with 8-bit
> characters when you use the web interface for Gmail.  If you Google
> "rfc 2047 vs rfc2231" you can get an idea of what happened (Chrome and
> Thunderbird support it for decode, and Google uses that as
> justification for keeping it ... and Chrome and Thunderbird don't want
> to disable that support, because Gmail still uses it.  Argh).

That Chrome decodes the broken encoding isn't a reason for Gmail to
continue to produce it if Chrome decodes the correct content too?  Is
there somewhere where a Googler states that's the reason to keep
producing RFC-violating content?

We could do with a friendly Googler as an earpiece.  :-)  The ones I
know are all Xooglers now.  I wonder if Go's
https://golang.org/pkg/net/mail/#ReadMessage cares.

I'm all for balking at handling it, similar to

    mhshow: "multipart/mixed" type in message 9740 must be encoded in
    7bit, 8bit, or binary, per RFC 2045 (6.4).  One workaround is to
    manually edit the file and change the "Quoted-printable"
    Content-Transfer-Encoding to one of those.  For now, continuing...

BTW, that "continuing..." means skipping that one particular
multipart/mixed type in that message?  It half implies "dealing with it
anyway, sigh".

Cheers, Ralph.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]