Using 9.4.0 on iOS 6. I have an email sent by a Mac which has no body, consists of just a png image. Using CreateForward gives me a CkoEmail with an unreadable image. I can see in the email source the forwarded email contains different data as the attachment, when normally the forwarded emails produced this way have the attachments contain the same base64 data. This is the email source in question:
From: XXXXXX XX@XX.XX Content-Type: image/png; x-mac-hide-extension=yes; x-unix-mode=0644; name="Screen Shot 2013-03-10 at 12.54.41 PM.png" Content-Transfer-Encoding: base64 X-Smtp-Server: mail.xxx.com:xxx Subject:  film recyc. Message-Id: <13AB4745-9C60-4C67-BF75-5A144B1975C9@XXX.com> X-Universally-Unique-Identifier: ee53269d-0cea-4805-b87c-ecad5fd9fc25 Date: Sun, 10 Mar 2013 12:58:19 -0400 To: XXXXXX XX@XX.XX Mime-Version: 1.0 (Mac OS X Mail 6.2 (1499)) Content-Disposition: inline; filename="Screen Shot 2013-03-10 at 12.54.41 PM.png"
Followed by the base64 image data. Any idea what could be going on?
Ah! I thought about passing the "image" data of the forwarded email through a base64 decoder. The result was insightful:
-----Original Message----- From: XXXXXX XX@XX.XX Sent: Sun, 10 Mar 2013 12:58:19 -0400 ...
So the entire forwarded message is encoded in place of just the png image. I haven't seen this before for other types of emails with attachments, so I guess it is something in this particular message sent by mac mail.
If someone wants to test it out, the above mail was created by composing a new email in Mac OS X's Mail.app, adding an email attachment (by clicking the attach button and NOT drag & drop) and perhaps a subject but leaving the email body empty.