That's what I implemented in mhfixmsg: just Content-Type name and Content-Disposition filename.
I think we're all fine with that; I'm wondering if we should see if it's an RFC 2047-encoded filename and just decode it automatically. --Ken _______________________________________________ Nmh-workers mailing list Nmh-workers(_at_)nongnu(_dot_)org https://lists.nongnu.org/mailman/listinfo/nmh-workers
Previous by Date: | Re: [Nmh-workers] RFC 2047 vs RFC 2231 encoding for MIME parameters, David Levine |
---|---|
Next by Date: | Re: [Nmh-workers] RFC 2047 vs RFC 2231 encoding for MIME parameters, Valdis . Kletnieks |
Previous by Thread: | Re: [Nmh-workers] RFC 2047 vs RFC 2231 encoding for MIME parameters, David Levine |
Next by Thread: | Re: [Nmh-workers] RFC 2047 vs RFC 2231 encoding for MIME parameters, Valdis . Kletnieks |
Indexes: | [Date] [Thread] [Top] [All Lists] |