What's the (config file?) fix so the string in filename=SOME_UTF-8_CODED_STRING associated w/below attachment headers is properly decoded?
Expanding on this a bit ... it is unequivocally WRONG for things like MIME parameters to be encoded using RFC 2047 rules (it's explicitly prohibited in the RFCs). There is a different encoding scheme for MIME parameters that nmh supports. But I know that some MUAs do this wrong. Sigh. --Ken -- nmh-workers https://lists.nongnu.org/mailman/listinfo/nmh-workers
<Prev in Thread] | Current Thread | [Next in Thread> |
---|---|---|
|
Previous by Date: | Re: [nmh-workers] procmail/rcvstore & message file format, David Levine |
---|---|
Next by Date: | Re: [nmh-workers] Quoting non-ASCII in reply, Ken Hornstein |
Previous by Thread: | Re: [nmh-workers] mhstore saving pdf w/o decoding filename- soln apparently: mhfixmsg, valdis . kletnieks |
Next by Thread: | [nmh-workers] Quoting non-ASCII in reply, Conrad Hughes |
Indexes: | [Date] [Thread] [Top] [All Lists] |