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
unconditionally.
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.
David
_______________________________________________
Nmh-workers mailing list
Nmh-workers(_at_)nongnu(_dot_)org
https://lists.nongnu.org/mailman/listinfo/nmh-workers