Open
Bug 540185
Opened 15 years ago
Updated 2 years ago
TB does not correctly include the email when forwarding ( multipart/related[ multipart/alternative[ text/plain+text/html ] + {image/jpeg with Content-Id: and Content-Location: which is different from Content-Id:} ] )
Categories
(Thunderbird :: Message Compose Window, defect)
Thunderbird
Message Compose Window
Tracking
(Not tracked)
NEW
People
(Reporter: guilherme.map, Unassigned)
References
(Blocks 1 open bug)
Details
(Keywords: testcase)
Attachments
(2 files)
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2) Gecko/20100105 Firefox/3.6
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2pre) Gecko/20100115 Lanikai/3.1a1pre
For some messages, when I click on TB to forward a message, when the composition window appears, the original message does not appear on the new message. If I click on TB to reply instead of forward, the message appears perfectly.
It also happens on TB 3.0 and 2.x
Reproducible: Sometimes
Steps to Reproduce:
1. Just click to forward a message
2. The new message window appears
3. The original message should be included
Actual Results:
The original message is not included.
|
||
Comment 3•15 years ago
|
||
(In reply to comment #1)
> Created an attachment (id=422015) [details]
> A message that shows the behavior I explained
Confirming on Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.2pre) Gecko/20100117 Lanikai/3.1a1pre
Message is of type MIME-Version: 1.0
Content-Type: multipart/related;
type="multipart/alternative";
This might be bug 479203 symptoms are the same.
|
|
||
Updated•15 years ago
|
Status: UNCONFIRMED → NEW
Ever confirmed: true
|
||
Updated•14 years ago
|
Summary: TB does not correctly include the email when forwarding → TB does not correctly include the email when forwarding ( multipart/related[ multipart/alternative[ text/plain+text/html ] + image/jpeg ] )
|
|
||
Comment 4•14 years ago
|
||
Guilherme this might have been fixed by bug 351224. Could you take a few minutes and download the latest nightly ( http://ftp.mozilla.org/pub/mozilla.org/thunderbird/nightly/latest-comm-central/ ), backup your profile and test and let us know if this is fixed or not ?
|
|
||
Updated•13 years ago
|
Attachment #422015 -
Attachment mime type: message/rfc822 → text/plain
|
|
||
Updated•13 years ago
|
Attachment #422016 -
Attachment mime type: message/rfc822 → text/plain
|
|
||
Updated•13 years ago
|
Summary: TB does not correctly include the email when forwarding ( multipart/related[ multipart/alternative[ text/plain+text/html ] + image/jpeg ] ) → TB does not correctly include the email when forwarding ( multipart/related[ multipart/alternative[ text/plain+text/html ] + {image/jpeg of Content-Id: with Content-Location: of different string from Content-Id:} ] )
|
|
||
Comment 6•13 years ago
|
||
FYI.
Attached mail had Content-Location: in embed image/xxx part. This produced problem of bug 689964, and it affect on embed image display.
Analysis of "problem after problem ... after bug 689964" is useless. Please rule out problem by bug 689964 from this bug.
|
|
||
Updated•13 years ago
|
Summary: TB does not correctly include the email when forwarding ( multipart/related[ multipart/alternative[ text/plain+text/html ] + {image/jpeg of Content-Id: with Content-Location: of different string from Content-Id:} ] ) → TB does not correctly include the email when forwarding ( multipart/related[ multipart/alternative[ text/plain+text/html ] + {image/jpeg with Content-Id: and Content-Location: which is different from Content-Id:} ] )
|
||
Comment 7•8 years ago
|
||
Can be reproduced with TB 49 (2016-05-17) with attachment 422015 [details] and attachment 422016 [details].
Both messages display fine, but when forwarding, they are incomplete.
We note that the MIME structure is incorrect:
Content-Type: multipart/related;
type="multipart/alternative";
boundary="----_=_NextPart_001_01CA5C82.C6742408"
doesn't make sense.
In general, a message with plain text and HTML with embedded images should be multipart/alternative and the second part, the HTML part, should be multipart/related to include the images.
TB doesn't handle bad MIME structures very gracefully. The workaround is to reply instead of forward.
Severity: major → normal
|
||
Updated•6 years ago
|
|
||
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•