>It's not as bad as all that - if you have the entire body handy, about the only >three things that you'd really need are the C-T-E from the main headers, the >main MIME type, and if it's a multipart/*, what the bodypart boundary string >is. And your Perl script already does 2 of those.
Actually, I've got the boundary string as well, since it's part of the Content-Type header. In my (brief) tests, my Perl script handles multiparts (including nested multiparts) just fine. >Mind you, the hard part is writing the code to figure out what to *do* with >a multipart/alternative that's got a message/rfc822 as one of the parts, >yadda yadda yadda. ;) Yeah, I decided to punt for all message/* types. I couldn't ever remember a time when I needed to have the content of a message/* part in a reply. In theory the code wouldn't be so bad since Mailtools has all of the pieces in it to parse a rfc822 header, but I decided to let people see what I have now. --Ken _______________________________________________ Nmh-workers mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/nmh-workers
