Closed Bug 215313 Opened 21 years ago Closed 20 years ago

Multipart/mixed MIME messages may not display body

Categories

(Thunderbird :: Mail Window Front End, defect)

x86
Windows XP
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 149771

People

(Reporter: larry, Assigned: mscott)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5a) Gecko/20030728 Mozilla Firebird/0.6.1 Build Identifier: Mozilla Thunderbird 0.1 (20030723) Mozilla bug 148771 also exists in Thurderbird 0.1. http://bugzilla.mozilla.org/show_bug.cgi?id=149771 I am adding this bug because I don't whether this derives from the common code-base or not. Reproducible: Always Steps to Reproduce: 1. 2. 3.
Oops -- make that bug 149771 (not bug 148771). Thanks.
I have experienced this as well. Mostly with messages imported from Eudora.
I have been seeing this with messages originating from OE 5.5 and up on news server news.annexcafe.com. In one case the news admin had to email me so I could read an important staff announcment.
QA Contact: asa
I have seen this too, especially with imported messages from Eudora as well (using TB 0.2)
Still happening to me as of TBird release 20031026. For me, it happens for about 75% of messages that contain attachments and does not seem to follow a pattern based on sending mail client. Messages instead display "This body part will be downloaded on demand." Original message will display if "View" -> "Message Body As" -> "Plain Text" is selected.
I get the message for some mail in Mozilla 1.6 too: This body part will be downloaded on demand.
I have the same experiences. Message "This body part will be downloaded on demand." appears when I replay this mail too, but when I forward this mail appears the orginal mail body. Release - Thunderbird 0.3.
In Thunderbird 0.5 (20040207) a multipart/mixed MIME message with a single part text/plain part does not display (no attachments are shown when the mail is opened), unless "View | Display Attachments Inline" is selected. Example follows: ------------------------------------- From ..snip.. Return-Path: ..snip.. Received: ..snip.. Content-Transfer-Encoding: binary Content-Type: multipart/mixed; boundary="_----------=_1078164153287260" MIME-Version: 1.0 X-Mailer: MIME::Lite 2.117 (F2.6; B2.12; Q2.03) Date: Mon, 1 Mar 2004 18:02:33 UT Subject: attachment will not display To: fred@allen-sauer.com From: fred@allen-sauer.com Message-Id: <20040301180236.AE91278098@zephyr02> Status: RO X-Status: X-Keywords: NonJunk X-UID: 51 This is a multi-part message in MIME format. --_----------=_1078164153287260 Content-Disposition: inline; filename="20040227-201420-mp-clickfreegifts.txt" Content-Transfer-Encoding: 7bit Content-Type: text/plain; name="20040227-201420-mp-clickfreegifts.txt" this is the text of the attachment which will not display unless "View | Display Attachments Inline" is specified --_----------=_1078164153287260--
I wonder if this is related to bug 147265 ?
This happens to me a lot. I can read the text of the message by reading the source. The message is there, it is just not being displayed. Source of sample mail message: (private details omitted) From - Tue Aug 10 06:22:57 2004 X-UIDL: 41183fed00000001 X-Mozilla-Status: 0001 X-Mozilla-Status2: 00000000 Return-Path: <xxxxxxt.xxxxxa@sympatico.ca> X-Original-To: xxxxxxx@keh.co.il Delivered-To: xxxxxxx@keh.co.il Received: from mail.ein-hashofet.co.il (unknown [127.0.0.1]) by localhost (Postfix) with ESMTP id B00BC720069 for <a_levita@keh.co.il>; Mon, 9 Aug 2004 20:41:54 +0000 (UTC) Received: from tomts5-srv.bellnexxia.net (tomts5.bellnexxia.net [209.226.175.25]) by mail.ein-hashofet.co.il (Postfix) with ESMTP id 525DA720070 for <xxxxxxxxx@keh.co.il>; Mon, 9 Aug 2004 23:41:52 +0300 (IDT) Received: from hppav ([65.95.41.190]) by tomts5-srv.bellnexxia.net (InterMail vM.5.01.06.10 201-253-122-130-110-20040306) with SMTP id <20040809204213.UZNZ1984.tomts5-srv.bellnexxia.net@hppav>; Mon, 9 Aug 2004 16:42:13 -0400 Message-ID: <001a01c47e51$3f8d6ba0$30b9fea9@hppav> From: "Robert L" <robert.xxxxxxxx@sympatico.ca> To: "AlanSpare" <xxxxxxxxxxx@ein-hashofet.co.il>, "Alan xxxxxx" <xxxxxxxxx@keh.co.il>, "ALAN" <xxxxxxxxxx@ein-hashofet.co.il> Subject: Here's my e-mail again. Date: Mon, 9 Aug 2004 16:41:29 -0400 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0017_01C47E2F.B85298C0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1409 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409 Status: This is a multi-part message in MIME format. ------=_NextPart_000_0017_01C47E2F.B85298C0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi Alan: Can you call xxxxxxxx yyyyyyyyyy and tell him you need some money. You have about $****** in your account, and S***** will need some to buy = your ###### and other stuff in the next two weeks. We plan to take &&&&&&&& out for his birthday lunch next weekend (he = doesn't know it yet), so if you mention the money to him this week, = he'll call here, and we can get a cheque from him when we see him. Please acknowledge this letter and that you've called ========. ME ------=_NextPart_000_0017_01C47E2F.B85298C0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD> <META http-equiv=3DContent-Type content=3D"text/html; = charset=3Diso-8859-1"> <META content=3D"MSHTML 6.00.2800.1400" name=3DGENERATOR> <STYLE></STYLE> </HEAD> <BODY bgColor=3D#ffffff> <DIV><FONT face=3DArial size=3D2> <DIV><FONT face=3DArial size=3D2>Hi Alan:</FONT></DIV> <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV> <DIV><FONT face=3DArial size=3D2>Can you call ========== and tell him = you need some=20 money.</FONT></DIV> <DIV><FONT face=3DArial size=3D2>You have about $$$$$$ in your account, = and Spppppp will=20 need some to buy your ^^^^^^ and other stuff in the next two = weeks.</FONT></DIV> <DIV><FONT face=3DArial size=3D2>We plan to take&nbsp;%%%%% out for his = birthday=20 lunch next weekend (he doesn't know it yet), so if you mention the money = to him=20 this week, he'll call here, and we can get a cheque from him when we see = him.</FONT></DIV> <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV> <DIV><FONT face=3DArial size=3D2>Please acknowledge this letter and that = you've=20 called ++++++++.</FONT></DIV> <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV> <DIV><FONT face=3DArial size=3D2>ME</FONT></DIV> <DIV>&nbsp;</DIV></FONT></DIV></BODY></HTML> ------=_NextPart_000_0017_01C47E2F.B85298C0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Your Message Was Checked And found to be clean email-body was scanned and no virus found email-body was scanned and no virus found ------ Trendmicro VirusWall on (mail.ein-hashofet.co.il) ---------- ------=_NextPart_000_0017_01C47E2F.B85298C0--
Similar (I think same) bug exist on 0.7.3. It looks like when thunderbird meets (1) A multipart/mixed message (2) One of part is not properly terminated (i.e. without separator, by buggy MTA or as a result of divided message), it just shows blank page.
re: comment #11 Are you sure it is only affecting "malformed" mime/multi-part mixed messages? What terminator is missing in the message? I see this so often, that I am wondering if it isn't more widespread than just broken messages.
With Thunderbird 1.0.1 (Linux), I also see this if "Display Attachments Inline" is not selected. It appears that Thunderbird (at least as of 0.6) is particularly guilty of creating unviewable bodies. See, for example (some headers omitted): ------------------------>8 SNIP 8<------------------------- User-Agent: Mozilla Thunderbird 0.6 (X11/20040519) MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="------------090705000300080701010308" This is a multi-part message in MIME format. --------------090705000300080701010308 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Also, please send me status on recruiting today. Here's the status I have, if I forgot to record something you did, chastise away. --------------090705000300080701010308 Content-Type: text/plain; name="Dev Michael Rieser-cover.txt" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="Dev Michael Rieser-cover.txt" ------------------------>8 SNIP 8<------------------------- In contrast, the following from outlook views OK on Thunderbird 1.0.1: ------------------------>8 SNIP 8<------------------------- MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----_=_NextPart_001_01C5474C.BB663469" Content-class: urn:content-classes:message This is a multi-part message in MIME format. ------_=_NextPart_001_01C5474C.BB663469 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable All,=20 I need all of you to try to make time to interview Ellen Zhang for the QA role.=20 She will be here at 11:30 am CST today. This is short notice so well need to just be flexible.=20 Ill follow up ------_=_NextPart_001_01C5474C.BB663469 Content-Type: application/msword; name="Ellen Zhang.doc" Content-Transfer-Encoding: base64 Content-Description: Ellen Zhang.doc Content-Disposition: attachment; filename="Ellen Zhang.doc" ------------------------>8 SNIP 8<------------------------- Perhaps it's the Content-Encoding, perhaps the format=flowed; I just don't know. Thanks, --kirby
Fred Sauer's problem (comment 8) is bug 182627 / bug 229075. "et-tu-mozilla"'s problem (comment 10) is a malformed message, as discussed at bug 101719. Kirby Files gave no details on the exact issues with the display, so I can't really be sure what's going on there. The two messages presented as examples really aren't comparable. (In reply to comment #0) > Mozilla [bug 149771] also exists in Thurderbird 0.1. > > I am adding this bug because I don't whether this derives from the common > code-base or not. It is from the common code base. Assuming you were correct in identifying your original problem, I'm duping this bug to that. *** This bug has been marked as a duplicate of 149771 ***
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.