This is actually quite a difficult task, much harder than i had anticipated. I have been playing with the following code which produces some weird behavior: 
!/usr/bin/perl 
#use Email::MIME; 
use Email::Simple; 
use Data::Dumper; 
use MIME::Parser; 
use HTML::SimpleParse; 
use strict; 
use warnings; 
undef $/; 
 
my $message = <>; 
my $email = Email::Simple->new($message); 
 
 
print $email->header("To"),"\t",$email->header('Content-Type'), "\n"; 
 
 
my $parser = new MIME::Parser; 
my $data = $parser->parse($email->body); 
my $results = $parser->results; 
print Dumper($results);

[download]
I dont know how to handle messages cases where messages are mime/not mime. Plus this doesnt actually seem to "parse" the message. The MIME metadata still is still within the email. suggestions? Thanks!

In reply to Re^2: Robust parsing of email messages by downer
in thread Robust parsing of email messages by downer

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.