>Nice of you to take the blame, but the real blame is the brain dead >parsing code in mhonarc, which appears I never really tested. Why the >problem was never discovered before is beyond me (likely since attribute >parts are rarely used in the wild).
I don't look at the headers of every message I get, but I did check my mailbox for examples when I was writing the RFC 2231 parser. I have never seen an extended MIME parameter on a Content-Type header "in the wild", but I do see them all of the time on Content-Disposition headers (when the filenames get really long). So if you're not parsing the Content-Disposition header, it doesn't surprise me that you'd never encounter them; when you think about it, there really aren't that many MIME parameters out there in common use. >I've updated the archiving software on mhonarc.org that contains a fix >to the problem, so the nmh-workers (HTML) archive there should be >updating again: <http://www.mhonarc.org/archive/html/nmh-workers/>. Thanks! --Ken _______________________________________________ Nmh-workers mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/nmh-workers
