566436 - Attachment corruption and message bodies will not load in preview pane or messaging window.

Status: RESOLVED INCOMPLETE

(Thunderbird :: General, defect)

Description

[bamrhein]

User-Agent:       Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.3) Gecko/20100423 Ubuntu/10.04 (lucid) Firefox/3.6.3
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.9) Gecko/20100317 Lightning/1.0b1 Thunderbird/3.0.4

Having a user rebuild their index usually seems to fix the following 3 issues:

1) Forwarding an email corrupts attachments - rebuilding index allows attachments to be opened and forwarded
2) Message bodies will not load in preview pane or message window - even if Thunderbird is closed and reopened.
3) Message body says that it will be downloaded upon request - rebuilding index makes it download. Even manually marking it for download does not download it, again even after close and reopen.

Reproducible: Sometimes

Steps to Reproduce:
1. Forwarding emails with attachments
Actual Results:  
The attachments become corrupted. Re-building the index seems to temporarily fix this issue.

Expected Results:  
Attachments should stay intact when being forwarded.

Email messages should always be viewable in the preview pane and in the message window when called for.

Message body shouldn't need to be downloaded upon request...

Comment 1

[Nicholas Baldridge]

This happens in Windows XP to most users at one time or another.  A few users are using the 3.1RC since 2010-05-27, and so far have not had to rebuild their index.

Thanks,
-Nick

Comment 2

[Wayne Mery (:wsmwk)]

Do you still see this issue when using version 5 or 6 (due out in a week)?
- If you no longer see the problem, please set status to RESOLVED, and set resolution to WORKSFORME. (or perhaps INVALID, if you determined the problem is not Thunderbird)
- If you still see the problem, please provide updated details, and any additional steps needed to reproduce the problem.

Comment 3

[Joshua Cranmer [:jcranmer]]

RESOLVED INCOMPLETE due to lack of response to previous question. If you feel this change was in error, please respond to this bug with your reasons why.