559794 - Images in messages from The bat! (4.2.33) senders doesn't show

Status: RESOLVED DUPLICATE of bug 61815

(Thunderbird :: General, defect)

Description

[Altaveron]

User-Agent:       Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.2.3) Gecko/20100401 Firefox/3.6.3
Build Identifier: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.1.9) Gecko/20100317 Thunderbird/3.0.4

Bug is critical. All The bat! messages with images are broken in Thunderbird. (Other mail clients work fine.)

Reproducible: Always

Steps to Reproduce:
1. Install the latest version of The Bat! (4.2.33).
2. Create a new message with an image by The Bat! (you may find the same message in the attachment).
3. Read the message by the latest version of the Thunderbird (3.0.4).
Actual Results:  
The image doesn't show.

Expected Results:  
The image should be shown.

We may find in the message source the following code:

<img width=3D234 height=3D55 alt=3D"" hspace=3D1 vspace=3D1 src=3D"cid:C86B=
CD3B.01CADD5B.1162047D.752B0E75_csseditor">

Content-ID: <C86BCD3B.01CADD5B.1162047D.752B0E75_csseditor>

Thunderbird should automatically delete '=' symbols but doesn't do this.

Comment 1

[Altaveron]

Attachment: A typical message from The Bat! 4.2.33 that is broken in Thunderbird 3.0.4.

All private data were replaced by *****.

Comment 2

[Altaveron]

Attachment: A screenshot of the bug.

Comment 3

[Ludovic Hirlimann [:Usul]]

Hum <img width=3D234 height=3D55 alt=3D"" hspace=3D1 vspace=3D1 src=3D"cid:C86B=
CD3B.01CADD5B.1162047D.752B0E75_csseditor"></body>

The cid is chopped in it's middle by a single space, that might be the reason why we fail to display it. but reading http://en.wikipedia.org/wiki/Quoted-printable implies that it's soft breakage introduced by the format.


This is bug 61815

Comment 4

[Ludovic Hirlimann [:Usul]]

(In reply to comment #2)
> Created an attachment (id=439512) [details]
> A screenshot of the bug.

And that's what i get with the testcase of bug 61815

Comment 5

[Altaveron]

Please anybody fix this issue right now.