Umesh Shankar Reporter
	Description • 21 years ago

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7b) Gecko/20040421
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7b) Gecko/20040421

I received a message with a 2.2MB Word document attachment (3.3 MB message
size). The message shows up in the message list, but if I click on it, it will
not show up in the preview pane (the previous message I viewed just stays
there), and double-clicking does nothing. The message also cannot be moved or
copied. 

This happened once before a long time ago, and I seem to remember that being a
Word document as well, though not as large. Perhaps it is related to the MIME
type too?

The message downloads correctly in Pine.

Reproducible: Always
Steps to Reproduce:
1. Send very large (> 2MB) attachment; possibly needs to be a Word document
2. Receiver sees message in message list, tries to click on it

Actual Results:  
When I tried to reproduce by sending the document to myself, I was able to
access the message after it first downloaded, but when I clicked to another
folder and then back to the inbox, the problem was there.

Expected Results:  
The message should display and be manipulated normally.

	Ken
	Comment 1 • 20 years ago

I can confirm this on Win32, Thunderbird 0.8, using IMAP.

	Troodon
	Comment 2 • 20 years ago

Reporter, could you wait a few minutes to see if the message is opened? If it
is, could you try to delete the attachment and see if the problem persists with
a text only message?

It tried to reproduce this bug in Mozilla Mozilla/5.0 (Windows; U; Windows NT
5.0; en-US; rv:1.8a5) Gecko/20041113 and Thunderbird 0.9 (20041103) with big
attachments (up to 50 MB) and no so much text (about 50 KB), and both worked
fine, although I was able to reproduce with both the bug 238440

	Gervase Markham [:gerv]
	Comment 3 • 19 years ago

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/

	Gervase Markham [:gerv]
	Comment 4 • 19 years ago

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.