Ouch! can you trust all those email apps to map the same content to the same content-mime-type consistently?
In the meantime I went back to Email::MIME and had good results (for my one multipart test email) with its walk_parts().
my $client = Mail::IMAPClient->new(...);
# ... search mail box
my $parsed = Email::MIME->new($client->message_string($msgid))
+;
my @parts_to_save;
$parsed->walk_parts(sub { push @parts_to_save, $_[0] });
# the [0] is the whole message, rest are all parts including n
+ested
for (@parts_to_save){ print $_->as_string }
Email::MIME has also a t/nested-parts.t which I used to check that it works fine for nested parts.
And it seems I am leaving the dreadfull world of email.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|