An example that I have that is working with option A. Even though the raw data is clearly base64 encoded it is being parsed as a human readable string
$tmp_part->bodyhandle->as_string
There is no "Content-Encoding" header in the raw mail.
Here's the relevant part of the header:
X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:cont
+ent-classes:message MIME-Version: 1.0
Content-Type: multipart/related;
type="multipart/alternative";
boundary="----_=NextPart001_01CDF2E2.B6A090C6"
This is a multi-part message in MIME format.
------_=NextPart001_01CDF2E2.B6A090C6 Content-Type: multipart/alternat
+ive;
boundary="----_=NextPart002_01CDF2E2.B6A090C6"
------_=NextPart002_01CDF2E2.B6A090C6 Content-Type: text/plain;
charset="utf-8"
Content-Transfer-Encoding: base64
SGkgU3VlICwKCldpbGwgYmUgaW4gdG91Y2ggaSBhbSB0aGlua2luZyBvZiBkb2luZyBhIH
+RyaXAg dG8gSXRhbH
...
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.