User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:188.8.131.52) Gecko/20071008 SeaMonkey/1.1.5 Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:184.108.40.206) Gecko/20071008 SeaMonkey/1.1.5 A mail attachment is corrupted when the file is saved. The same exact mail message using a different client saves the attachment correctly. In this case, the mail attachment is a Flash video file. The SeaMonkey saved file will not play, but the same attachment saved with a different client plays fine. The original file that is the source of the attachment plays fine on the source machine. Reproducible: Always Steps to Reproduce: 1. Send a Flash video file as a mail attachment. 2. Save that attachment using the SeaMonkey client. 3. Note that the saved Flash video file will not play. 4. Save the exact same attachment with a different mail client and note that the Flash video file plays correctly. Actual Results: The Flash video file is corrupt. Expected Results: The Flash video file is not corrupt. The correct file size is 4,266,127 bytes, but the corrupt file size is 4,266,554.
Can you try SeaMonkey v1.1.9 ? (And v2.0a1pre ?) Can you attach the involved message (including its attached file) ? Or at least the Flash file ? So someone can try and reproduce. NB: If the file is 4 MB, you'll need to zip it, or, probably, make it available on a Ftp/Http site. Or keep it available to email it to someone who would look at this bug.
Version: unspecified → SeaMonkey 1.1 Branch
I am currently running SeaMonkey 1.1.9, but I have not recently received any emails with large file attachements. The original Flash video file was very large. Sorry, I no longer have the email with the large file attachment that caused this problem. I am aware of this problem, and if it happens again, I will update this incident. You may be able to reproduce this problem by attaching any large file that is many MBs in size.
Thanks for your answer. *** R.Incomplete. (for now) Reopen if/when you can reproduce with SeaMonkey v1.1.9.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 10 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.