MIME explains how to decode the email, you do want to check out the RFCs both 822 and 2822 for study,
http://www.faqs.org/rfcs/rfc2822.html
MIME, Multipupose Internet Mail Extensions, lets you send multiple pieces of different data in one message (say, a picture and a Word document), and it tells the recipient's email client what format the data is in so they can make smart choices displaying the message
Your email is in ASCII with rules, try decoding the Gibberish using a ASCII chart or BASE64 chart?
the ASCII characters making up the field-body, as
defined in the following sections, and consisting
of combinations of atom, quoted-string, and
specials tokens, or else consisting of texts
There are complex methods to decode the email manually, by taking it apart. You should be able to find tools, in various coding languages that can do this for you. Just search for MIME decode.
First download the contents of the email message.
Step 1
Check the "Content-Type" header. If the content type is multipart (i.e. "multipart/mixed", "multipart/alternative", etc) the message will have multiple sections to parse. If the content type is multipart, continue with below steps.
Step 2 The Content-Type header should contain a unique string used by the code that generated the MIME message to designate MIME part boundaries. Example: Content-Type: multipart/mixed; boundary="part_c7161025_fe8a_45f4_83ef_6befcfa5d021" The boundary string in this case is "part_c7161025_fe8a_45f4_83ef_6befcfa5d021".
Step 3 Each MIME part will be separated by the boundary string preceeded by two dashes ("--") on a blank line. You will need to scan the message line by line looking for the part boundaries. All text in between the boundaries *except the final CR/LF* is part of that MIME part. Important: The last MIME part will end with the boundary string followed by two more dashes. Example: --part_c7161025_fe8a_45f4_83ef_6befcfa5d021 First MIME part. --part_c7161025_fe8a_45f4_83ef_6befcfa5d021 Second MIME part --part_c7161025_fe8a_45f4_83ef_6befcfa5d021 Last MIME part. --part_c7161025_fe8a_45f4_83ef_6befcfa5d021--
Step 4 Each MIME part then needs to be parsed. The format of each MIME part is similar to the original RFC/822 formatted message. It will contain a series of headers, followed by a blank line, then the body data.
Step 5 A MIME part can itself be multipart, with its own "Content-Type" header and boundary string. Your code must recursively parse MIME parts until it reaches the child nodes.
Step 6 A MIME part can simply be a binary attachment. In this case a Filename header will usually be supplied, along with the transfer encoding. BASE64 is a popular encoding type. In this case the entire MIME part body must be BASE64 decoded. As an example here are the first few lines of an attached JPG image: ------_=_NextPart_003_01C755EF.43F2628D Content-Type: image/jpeg; name="testimage.jpg" Content-Transfer-Encoding: base64 Content-Description: testimage.jpg Content-Disposition: attachment; filename="testimage.jpg" /9j/4AAQSkZJRgABAQEAYABgAAD/2wBDAAgGBgcGBQgHBwcJCQgKDBQNDAsLDBkSEw8UHRofHh0a HBwgJC4nICIsIxwcKDcpLDAxNDQ0Hyc5PTgyPC4zNDL/2wBDAQkJCQwLDBgNDRgyIRwhMjIyMjIy MjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjL/wAARCAQABQQDASIA AhEBAxEB/8QAHwAAAQUBAQEBAQEAAAAAAAAAAAECAwQFBgcICQoL/8QAtRAAAgEDAwIEAwUFBAQA
Step 7 The HTML body of the message should be in a MIME section with ContentType: Text/Html, inside a ContentType: Multipart/Alternative MIME section.
Step 8 The plaintext body of the message should be in a MIME section with ContentType: Text/plain, inside a ContentType: Multipart/Alternative MIME section.
Have fun!
DNR
