Re: Thunderbird base64 images?

On Sat, 7 May 2016 01:02:20 UTC, Dave Yeo <[email protected]> 
wrote:

> On 05/06/16 09:40 AM, Barbara wrote:
> > On Fri, 6 May 2016 15:15:10 UTC, Dave Yeo <[email protected]>
> > wrote:
> >
> >> Barbara wrote:
> >>> I'm using Thunderbird 31.8.0 for email.
> >>>
> >>> Has anyone managed to correctly display a Thunderbird email which has
> >>> a couple of base64 formatted images which need to be decoded?
> >>>
> >>> So far as I can determine, the email is an html page from my cell
> >>> phone service to confirm autopay charges.  I can read the plain text
> >>> part, but the images are blank.
> >>>
> >>> gmail is my email client, and my iPhone displays the email correctly.
> >>>
> >>> This is not a big problem.... Just curious.
> >>>
> >>
> >> Have you tried right-clicking on an image and choosing display or
> >> similar? IIRC TB by default dowen't show images fo security reasons but
> >> there is a setting somewhere to change this
> >> Dave
> >
> > Yes, I'm familiar with the "To protect your security...." bar that
> > pops up for "normal" html pages where you can click "preferences" to
> > display images, but for the base64 coded image pages that bar does not
> > appear.  Right-clicking has no "display" option.
> >
> > No big deal.  I just wish the phone service would send a plain text
> > email without cute pictures attached.   grrrrrrr.
> >
> >
> 
> Under View-->Message Body As, do you have Original HTML checked or 
> Simple HTML or Plain Text? Whichever, try changing to Original or Simple.
> Dave

The view I choose doesn't seem to make much difference as far as 
viewing the images.  I can read the text part, which has the 
information I really need like account number, date, phone number.. 
etc, but the images are a format Thunderbird cannot display.

The email header contains:

Subject: Purchase Confirmation
Content-Type: multipart/alternative;


I've tried a bunch of things like "File - Save as" and it comes out to
be named: Purchase Confirmation.eml  This file contains all of the 
various base64 parts that look like this:  (largely SNIPPED)   

=================================================

----boundary_117_830d9a03-5c00-4fa7-a4f8-81576d8602ba
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: base64

<snipped>
ICNkOWQ5ZDkgc29saWQ7ICBwYWRkaW5nLWxlZnQ6IDEwcHg7IHBhZGRpbmctcmlnaHQ6
IDEwcHg7IGhlaWdodDogODVweDsiPg0KCQkgICAgPHNwYW4gc3R5bGU9ImZvbnQtd2Vp
Z2h0OiBib2xkOyBja1xvcjogIzk1YjNkZDsiPkhlbGxvPC9zcGFuPjxiciAvPkJBUkJB
----boundary_117_830d9a03-5c00-4fa7-a4f8-81576d8602ba
Content-Type: multipart/related;
 boundary=--boundary_118_47379dbf-a52b-4b57-9ffe-8564559ff373;
 type="text/html"


----boundary_118_47379dbf-a52b-4b57-9ffe-8564559ff373
Content-Type: text/html
Content-Transfer-Encoding: base64

<smipped>
IGNvbG9yOiAjOTViM2RkOyI+UmVmZXJyYWwgSUQ8L3NwYW4+PGJyIC8+MTgzNjk5Mjwv
dGQ+PHRkIHN0eWxlPSJiYWNrZ3JvdW5kLWNvbG9yOiWyYmZiZjk7IHdpZHRoOiAxNjBw
eDsgIHBhZGRpbmctbGVmdDogMTBweDsgcGFkZGluZy1yaWdodDogMTBweDsgaGVpZ2h0
----boundary_118_47379dbf-a52b-4b57-9ffe-8564559ff373
Content-Type: application/octet-stream
Content-Transfer-Encoding: base64
Content-ID: <image_1>

<snipped>
iVBORw0KGgoAAAANSUhEUgAAASwAAABkCAYAAAA8AQ3AAAAAAXNSR0IArs4c6QAAAARn
QU1BAACxjwv8YQUAAAAgY0hSTQAAeiYAAICEAAD6AAAAgOgAAHUwAADqYAAAOpgAABdw
nLpRPAAAAAlwSFlzAAAuIgAALiIBquLdkgAASGlJREFUeF7tfQVYVN23/hq6kVBCRUBU
.......

====================================================

And so on....  I think there are 4 of them.

This email as received in Thunderbird, has 3 attachments labeled Part 
1.2.2, Part 1.2.3 and Part 1.2.4. which I assume are the base64 
images. If I detach them and rename them as Part 1.2.2.png, Part 
1.2.3.png and Part 1.2.4.png, I can view them separately in PMView, 
but of course not as a web page.  These are the images which 
Thunderbird sees as blank boxes.

Now that I've put you to sleep,   :)  I repeat that it's just not 
worth bothering with.  There are dozens of 'net complaints about 
Thunderbird of assorted versions not being able to display base64 
stuff.  There's even an add-on to assist, which adds this type of 
decoding, but it quit working in version 24.

Thanks for the suggestions.


-- 
Barbara