This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Lolu chungechunge lwabekwa kunqolobane. Uyacelwa ubuze umbuzo omusha uma udinga usizo.

Does TB 38.3 support emails from Apple IOS with imbedded images?

  • 6 uphendule
  • 1 inale nkinga
  • 1 view
  • Igcine ukuphendulwa ngu Matt

more options

I received an email from someone who is using an Apply device and TB does not display the embedded image, just the frame. The image appears to me to be in MIME protocol and BASE64. Does TB 38.3 support this?

When I look at the message source it shows:

 Content-Type: multipart/alternative; boundary="Apple-Mail....."
 Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\))

further into the message source I see:

 --Apple-Mail=_026D45DB-9F4F-4BB2-A940-43B342AD09FC
 Content-Transfer-Encoding: base64
 Content-Disposition: inline;
 	filename="the filename?.jpeg"
 Content-Type: image/jpeg;

name="the filename?.jpeg"

 Content-Id: <87CFCF64-823A-4A6A-9A2C-6E728947B41A>

followed by the base64 representation of the image and then two final MIME brackets from Apple Mail.

I received an email from someone who is using an Apply device and TB does not display the embedded image, just the frame. The image appears to me to be in MIME protocol and BASE64. Does TB 38.3 support this? When I look at the message source it shows: Content-Type: multipart/alternative; boundary="Apple-Mail....." Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\)) further into the message source I see: --Apple-Mail=_026D45DB-9F4F-4BB2-A940-43B342AD09FC Content-Transfer-Encoding: base64 Content-Disposition: inline; filename="the filename?.jpeg" Content-Type: image/jpeg; name="the filename?.jpeg" Content-Id: <87CFCF64-823A-4A6A-9A2C-6E728947B41A> followed by the base64 representation of the image and then two final MIME brackets from Apple Mail.

All Replies (6)

more options

Mime and Base 64 are absolutely standard parts of email and yes Thunderbird knows about them. IMHO it's what Apple's email products do with them that is the issue here. I've had several bad experiences with messages sent by Apple users. Apple don't seem to see a need to be compatible or consistent with existing standards.

more options

Mime and Base 64 are absolutely standard parts of email and yes Thunderbird knows about them. IMHO it's what Apple's email products do with them that is the issue here. I've had several bad experiences with messages sent by Apple users. Apple don't seem to see a need to be compatible or consistent with existing standards.

more options

So, do you have any idea what MIME rule Apple has broken here? Can I edit the message to fix it so I can send it to myself and get TB to correctly decode the Base64 image?

more options

Is there really a question mark in the image's file name?

more options

Sorry, have been away for awhile.

Yes, there really is a ? in the filename in the MIME segment: --Apple-Mail=_026D45DB-9F4F-4BB2-A940-43B342AD09FC Content-Transfer-Encoding: base64 Content-Disposition: inline; filename="Paul Barsevskis and ? at CSG:STM?.jpeg" Content-Type: image/jpeg; name="Paul Barsevskis and ? at CSG:STM?.jpeg" Content-Id: <87CFCF64-823A-4A6A-9A2C-6E728947B41A>

I guess I was being too careful with personal details from the sender.

The Base64 code follows the above Content-Id line after a blank line. Below the Base64 code I have: --Apple-Mail=_026D45DB-9F4F-4BB2-A940-43B342AD09FC--

--Apple-Mail=_CEA13DDC-0815-41F2-84E6-D3796F59C5D0-- without a blank line immediately preceding the first --Apple-Mail line. It appears to me I am missing a closing --Apple-Mail line that has the same id as the one that preceding the Base64 code. My assumption is that they are suppose to bracket the Mime content itself.

more options

just try removing the ? in the file name.