[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: David Levine
Subject: Re: [Nmh-workers] RFC 2047 vs RFC 2231 encoding for MIME parameters
Date: Wed, 28 Sep 2016 13:24:33 -0400

Ken wrote:

> The exact issue is that some MUAs will use RFC 2047 encoding
> for a filename that contains 8-bit characters when creating a
> Content-Disposition field.

> I am torn as to what to do here.  It feels somehow wrong to support this
> for decode natively, but I'm not completely convinced of that.  We have
> a number of email programs that get this wrong, including a very popular
> one.  This might be something perfect for mhfixmsg to deal with.  What
> do others think?

Sounds like a job for mhfixmsg, I'll look into it for 1.7.  It would
probably go into the small category of things that it fixes

The question remains of whether mhstore should decode 2047-encoded
filenames natively.  It'd be friendly and it's very unlikely that what
looks ike an encoded string isn't.  On the other hand, running mhfixmsg
shouldn't be prohibitive.


reply via email to

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