Closed Bug 272424 Opened 20 years ago Closed 19 years ago

mail item does not display

Categories

(Thunderbird :: Mail Window Front End, defect)

x86
Linux
defect
Not set
critical

Tracking

(Not tracked)

RESOLVED EXPIRED

People

(Reporter: gfox, Assigned: mscott)

Details

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0
Build Identifier: Mozilla Thunderbird version 0.9 (20041103)

I received an email messaged (with some binaries as MIME encoded attachments)
that simply doesn't display in Thunderbird. That is, I can see that I have a
message, that it has an attachment, and can read the message headers, but the
text isn't readable and I can't click to save or open the attachments. I *can*
read the message by using "View: Message source." And other email programs (I
tried it with Kmail) display the message just fine. But all I see is a blank space!

If this is useful, the format is
<Message headers>
This is a multi-part message in MIME format.

------=_NextPart_000_1A50D9_01C4D61F.9324A8C0
Content-Type: multipart/alternative;
boundary="----=_NextPart_001_1A50DA_01C4D61F.9324A8C0"
Content-Transfer-Encoding: binary
MIME-Version: 1.0
X-Mailer: MIME-tools 5.411 (Entity 5.404)


------=_NextPart_001_1A50DA_01C4D61F.9324A8C0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
charset="iso-8859-1"
Content-Disposition: inline


<Plain text message that doesn't display>

<HTML version of the message>

<binary attachments>


If I click on this message, I can't read it or get to the attachments (as
reported). If I then "View: Message source", keep that window open, view a
different message, and then come back to the message in question, voila, there
it is. 

Reproducible: Always
Steps to Reproduce:
Reproducible every time with this particular message, that is.

1. Close & re-start Thunderbird.
2. Click on the message. It doesn't display.
3. Open the message source, view another message, and come back and click on the
original message

Actual Results:  
Message doesn't display after (2) as expected, but does display after (3).

Expected Results:  
It should have displayed the message after (2) -- simply clicking on it.

The only thing that made me suspect the problem was that the pane displaying the
message list DOES indicate that there's an attachment there -- but neither the
content nor the attachment were visible in the viewing pane. I nearly deleted
the message!
The problem also persists within the Windows-release. JavaScript Console would 
display:
Error: uncaught exception: [Exception... "Component returned failure code: 
0x80004005 (NS_ERROR_FAILURE) [nsIObserverService.removeObserver]"  
nsresult: "0x80004005 (NS_ERROR_FAILURE)"  location: "JS frame :: 
chrome://global/content/bindings/browser.xml :: destroy :: line 569"  data: no]
When forwarding the message the message and attachments are displayed as it 
should be...
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:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/
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.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.