Closed Bug 310546 Opened 20 years ago Closed 20 years ago

Downloading large attachments >> 1MB from Exchange seems to produce corruption

Categories

(Thunderbird :: Mail Window Front End, defect)

Product:
Thunderbird
Component:
Mail Window Front End
Platform:
x86
Windows XP
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WORKSFORME

People

(Reporter: ChristianCallsen, Assigned: mscott)

Details

Attachments

(2 files)

mimetypes.rdf in my TB profile.
2.56 KB, application/rdf+xml
Details
Saved output from pressing CTRL-U while viewing message with 3 PDF attachments
146.17 KB, text/plain
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b4) Gecko/20050908 Firefox/1.4 Build Identifier: Mozilla Thunderbird 1.5 Beta 1 (20050916) When I receive large Email attachments - for example, large PDF files bigger than 1 MB (not a hard limit), either saving the attachment or downloading it to view produces a resulting corrupted attachment file. Using Microsoft's Web Access to Exchange lets me save the attachment also, and comparing the two binary files indicates that they are *not* identical. The sender does not use Thunderbird to compose the message. Reproducible: Always Steps to Reproduce: 1. Receive email with multi-MB attachment (say. large PDF) 2. Attachments are viewable. Click on attachment to open or right-click and save. 3. Attempt to view PDF attachment. Acrobat Reader complains with error in file. Actual Results: Attachment appeared corrupted. Using MS Web Access I downloaded the attachment (using Firefox). This copy of the attachment opens correctly. Expected Results: Not corrupted the downloaded attachment. Small attached PDF files - < 1MB - seem to work fine. Marking critical because attachment corruption is a disaster.
I haven't tried the suggestions in bug 92111 - since the download completes and the files appear to have the correct length.
For the particular set of PDF files, the difference appears to be the first line with completely "binary" content, around 11,800 bytes.
How are you accessing Exchange via TB - POP3?
Nope, IMAP.
what version of Exchange are you using? My guess is that this is an Exchange server imap problem, since, historically, Exchange has had problems with imap attachments. However, you can try generating a client-side imap protocol log by following these instructions - http://www.mozilla.org/quality/mailnews/mail-troubleshoot.html#imap and look at the log to see if the binary content is sent down correctly from the imap server. An other possibility is a virus checker on your machine intercepting the data stream and corrupting it.
See also bug 142517
Thanks for the pointer to bug 142517. The description of the problem sounds similar (i.e., can't open PDF file). What's interesting is that this used to be fine with TB 1.0x. I checked my mimetypes.rdf and it looks like there's only default data. I'll try to attach it to this bug.
My mimeTypes.rdf file since but 142517 suggests a corrupted file can cause problems.
Severity: critical → normal
I haven't tried with older versions of TB, but this problem didn't seem to exist in the 1.0 TB.
Just confirmed that Thunderbird 1.0.7 does NOT have this bug. In a particular Email I have with 4 attachments, two of which are large PDF files, 1.0.7 can load and display the PDF file by doubleclicking on the attachment and using Adobe Reader to read it. TB 1.5 Beta can not - I get an error from Reader. In other words: this seems to be a regression of some sort from 1.0.7 to 1.5. Setting version to 1.5 to indicate this. I'd like to propose increasing severity. I can't send you the Email because the contents is not public (company confidential).
Version: unspecified → 1.5
(In reply to comment #10) > I can't send you the Email because the contents is not public (company > confidential). Can you make one up? Just fetch some random PDFs from the web and create the message with those? The suggestion in comment 5 to create an imap protocol log while trying to access the corrupted file is still pertinent; and if you can create a separate log for the working (1.0.7) case, that could make it easier to track down.
An extra bit of information. In a recent Email I received from an Outlook user, I noticed that one of the PDF file attachments was *NOT* MIME encoded. I suppose PDF looks almost like ASCII text. I can attach the Email as seen from source view (CTRL-U).
Here's the Email. Notice that the 3rd attachment is NOT MIME encoded but just sent as "text" with ='s at the end. Maybe what we need to do when saving this is to carefully undo what Outlook did.
Guys, this might be a duplicate of 317009. *** This bug has been marked as a duplicate of 317009 ***
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → DUPLICATE
Yes, it could be, but until verified it isn't. Can anyway test to see if this bug disappears using a nightly?
Status: RESOLVED → UNCONFIRMED
Resolution: DUPLICATE → ---
Any particular nightly you'd liketo recommend?
The latest one?
Branch? Trunk? 1.5.0.x nightly? (there might be an obvious answer, but I want to make sure)
Trying ThunderBird 1.5 nightly, with build id "version 1.5 (20060131)" on Win32 (taken from the about panel) fixes this problem.
Perfect. Closing as WFM as we have no code to prove what fixed this problem although Bug #317009 seems like the most likely candidate.
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago → 20 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: