Closed Bug 373821 Opened 17 years ago Closed 16 years ago

Large IMAP emails that are stopped in transfer can result in broken client cache

Categories

(Thunderbird :: Mail Window Front End, defect)

x86
Windows XP
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 405440

People

(Reporter: al, Unassigned)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.10) Gecko/20070216 Firefox/1.5.0.10
Build Identifier: 1.5.0.10 (20070221)

In certain circumstances (described with a reproducible case below) if when you are receiving a large email via IMAP you press the "Stop the current transfer" button, you can leave TB's local cache of the message corrupt and thus unable to view the email.

The issue only occurs where the email is within in a folder that has been selected for offline use.

This issue will only affect users who "stop the current transfer".  This action is usually not possible except on large emails or where the network connection to the IMAP server is slow.  Therefore this cannot be affecting many users.

This occurs with both plain text and MIME messages.  My reproducible case provides an example with an embedded image, but the same fault occurs when using plain text.  Finding enough text to create a large enough email that will then take long enough to stop the transfer takes some doing (I used War & Peace: http://www.arcamax.com/fiction/b-1004 !).  It is easier to find attachments or images that can bump up the email to a sufficient size to witness the problem.

Limitations on my reproducible case, for you might be that your line speed may be quicker than mine (~800kB), so you may have to simply increase the number of images in your test case.

Reproducible: Always

Steps to Reproduce:
1. have ready an account accessible via IMAP, it should have a folder other than Inbox ready to use, the test folder should have at least one email in it and it must be selected for offline use.

2. create a message with 1 line of text.  Paste directly into the body an image of 200kB in size.  (this step need not use Thunderbird as the sending client.)

3. send it the IMAP account

4. refresh the IMAP Inbox

5. select the new Large Test Message, let it download and be satisified it is ok

6. select a different message

7. return to the Large Test Message, satisfy yourself it is ok

8. repeat (6) and (7)

9. now move the message to a different folder that has been selected for offline use

10. select the folder, refresh contents if necessary

11. select the Large Test Message, notice it starting to download (afresh), before it completes click the toolbar button "Stop the current transfer"

12. select a different message

13. select the Large Test Message again, this time allow it to download, notice now that the line of text appears, but the image does not.  Choose View, Message Source, notice how this is void.

14. select a different message

15. select the Large Test Message again, notice how the email message view window is void (and the View, Message Source is still void).

Workaround:
16. move the "broken" Large Test Message, move it to a different folder, then move it back, this time not interrupting the download and all is well again.
Actual Results:  
The email is void/broken

Expected Results:  
The email should display
dupe?
Assignee: mscott → nobody
Component: Message Compose Window → Mail Window Front End
QA Contact: message-compose → front-end
(In reply to comment #0)
>(a) a large email via IMAP
>(b) you press the "Stop the current transfer" button,
>(c) The issue only occurs where the email is within in a folder that has been selected for offline use.

It sounds problem of Bug 405440 which remained on offline-use folder even after fix of Bug 386514.
  Bug 386514 : fixed by Tb 2.0.0.5   Bug 405440 : fixed by Tb 2.0.0.12.

To AndrewL(bug opener):
Does your problem occur on latest Tb release? 
Confirmed fixed in Tb 2.0.0.12
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
FIXED means "patch for this bug resolved the problem".
This bug is earlier discovery, but already fixed by Bug 405440.
Sorry but duping to Bug 405440.
Resolution: FIXED → DUPLICATE
You need to log in before you can comment on or make changes to this bug.