On Wed, Feb 09, 2011 at 03:54:29PM -0500, Ed Blackman wrote: > On Wed, Feb 09, 2011 at 08:26:03PM +0000, Chris G wrote: > >On Wed, Feb 09, 2011 at 01:49:33PM -0500, Ed Blackman wrote: > >>You can tell Mutt to use RFC2047 decoding on MIME file names with > >> set rfc2047_parameters=yes > >> > >Would that be in addition to the 'normal' decoding which works with most > >attachments? I.e. would everything that worked before continue to work > >correctly? > > Yes. The only thing that might break (and I'm not even sure it > would) is if someone sent you a file actually named something like > "=?blah?Q?foo?". In other words, a legitimate file name that > *looks* like it's RFC2047 encoded, but actually isn't. > > In practice, most people don't send files with weird names like > that, and there's a large set of people who use non-compliant user > agents that send files with RFC2047 encoded names. > OK, thanks for all the information.
-- Chris Green
