Attachments not accessible



Mail Window Front End
14 years ago
12 years ago


(Reporter: Martin Mokrejs, Assigned: Scott MacGregor)


Firefox Tracking Flags

(Not tracked)



(1 attachment)



14 years ago
  I use cvs version of mozilla for some months, I update time to time. Now, I
don't see some attachments, although the "status" bar splitting right upper and
lower wframes in mailer shows the icon used for attachments. When I double click
the icon, there are no attachments.

  I did "Save as" and the file has attachment. It is forwarded email from PINE
MUA. Something is wrong in mozilla's mailer. I use on linux Mozilla/5.0 (X11; U;
Linux i686; en-US; rv:1.8a6) Gecko/20050102

Comment 1

14 years ago
Created attachment 170378 [details]
An email having attachment not parseable by mozilla
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Last Resolved: 13 years ago
Resolution: --- → EXPIRED

Comment 4

13 years ago
I see the attachment now but double-clicking the icon gives me:

###!!! ASSERTION: couldn't get message header: 'PR_FALSE', file nsMailboxProtocol.cpp, line 436
Break: at file nsMailboxProtocol.cpp, line 436
WARNING: NS_ENSURE_TRUE(NS_SUCCEEDED(rv)) failed, file nsMailboxService.cpp, line 641
WARNING: NS_ENSURE_TRUE(msg) failed, file nsMailboxUrl.cpp, line 495
WARNING: NS_ENSURE_TRUE(NS_SUCCEEDED(rv)) failed, file nsMailboxUrl.cpp, line 525

Download the testcase and use "File/Open file" from the mailer and doubleclick the attachment file (.doc file). Then you get the assertion.

Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9a1) Gecko/20051122 SeaMonkey/1.5a

 ./configure --disable-optimize --enable-debug='-g3 -O0' --enable-debug-modules=all --enable-debugger-info-modules --enable-detect-webshell-leaks --enable-svg --enable-svg-renderer-libart --enable-image-decoders=all --with-qtdir=/usr/qt/3 --enable-application=suite --disable-freetype2 --enable-default-toolkit=gtk2 --enable-xft --disable-gssapi
Resolution: EXPIRED → ---

Comment 5

13 years ago

I frequently receive emails with attachments that don't conform to standards i.e. the attachment is after the end-of-message mark (with -- on the end of MIME multipart boundary). It seems it was sent by a Microsoft Outlook.

I know that it's nonstandard but I'd be happy if Thunderbird could extract these attachments as they're there.

Example (stripped):

Received: from ([]) by with Microsoft SMTPSVC(6.0.3790.1830);
	 Mon, 11 Jan 2006 14:07:16 +0100
Message-ID: <......>
From: ...
To: ...
Subject: Fw: email
Date: Wed, 11 Jan 2006 14:06:24 +0100
MIME-Version: 1.0
Content-Type: multipart/mixed;

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

Content-Type: multipart/alternative;

Content-Type: text/plain;
Content-Transfer-Encoding: quoted-printable

Kedves Mindenki!=20

  _____ =20

Content-Type: text/html;
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns:o =3D "urn:schemas-microsoft-com:office:office"><HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =

<META content=3D"MSHTML 6.00.2900.2802" name=3DGENERATOR>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>
<P class=3DMsoNormal=20
style=3D"MARGIN: 0cm 0cm 0pt; TEXT-ALIGN: =





Content-Type: image/png;
Content-Transfer-Encoding: base64
Content-Disposition: attachment;


Content-Type: application/msword;
	name="idopont beosztas.doc"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
	filename="idopont beosztas.doc"



Comment 6

12 years ago
Martin Mokrejs, is this still a problem for you?  I just tried opening the sample message (via File|Open: errors in the console per bug 338536 but otherwise opened OK) and saved the message to disk with no problem or further error, using TB 1.5 and 2a1-0909 / X11, Debian.

Comment 7

12 years ago
Yes, I can open the attachment fine on linux with Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.13) Gecko/20060426. Do you want me to test current cvs version?

Comment 8

12 years ago
(In reply to comment #7)
> Yes, I can open the attachment fine on linux with Mozilla/5.0 (X11; U; Linux
> i686; en-US; rv:1.7.13) Gecko/20060426. Do you want me to test current cvs
> version?

You reported this bug on a pre-release 1.8 version; and comment 4 mentions 1.9.  It would be good if you could test with a current 1.8.1 branch build or a trunk build (1.9).

Comment 9

12 years ago
I can confirm with current cvs HEAD I can open the attachments. The clip icon is always shown regardless the Original HTML/Simple HTML/Plain text value set in View/"Message body as" menu item.

Last Resolved: 13 years ago12 years ago
Resolution: --- → FIXED


12 years ago
Resolution: FIXED → ---

Comment 10

12 years ago
Reopened to fix resolution.  In the future, please use Fixed only for bugs where you can point to a patch that fixed the problem.
Last Resolved: 12 years ago12 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.