286005 - Email attachments sent from Mozilla mail are corrupted.

Status: RESOLVED WORKSFORME

(MailNews Core :: Attachments, defect)

Description

[paitken]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-GB; rv:1.7.5) Gecko/20041217
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-GB; rv:1.7.5) Gecko/20041217

Mail attachments of sufficient size (yet to be determined) may contain random
memory contents which corrupt the outbound email.

Reproducible: Sometimes

Steps to Reproduce:
1. Compose short email.
2. Attach large enough file.
3. Send...

Actual Results:  
Email was sent. Everyone who received it saw it was corrupt. Corruption contains
random memory contents, eg sometimes contains URLs or recognisable phrases.

Expected Results:  
Should send uncorrupt attachments. Don't send random memory contents.

Comment 1

[paitken]

I really want to put this in the MailNews:Attachments Component, but I don't
have that option.

Comment 2

[paitken]

Occurs in 1.7.3 and 1.7.5.

Comment 3

[paitken]

Attachment: corrupted PDF file

Here's a short excerpt from a PDF file I sent. I tried to send more, but it's
not happening.

Normally this would be readable as a plain text file, but the binary corruption
prevents that.

I've stripped out some correctly? encoded stuff where indicated [...]

Note how the encoding is suddenly interspersed with random stuff - some of
which is almost recognisable.

Comment 4

[paitken]

Attachment: corrupted PDF, zipped

Compressed the larger file to see whether it sends OK.

Comment 5

[paitken]

I was unable to upload the second attachment (58,899 bytes) until I compressed
it (12,599 bytes).

So the issue may not be so much to do with the sending of email attachments as
with the uploading of local data?

Comment 6

[Andrew Schultz]

This is working ok for everyone else.  Can you try a clean profile?
% mozilla -ProfileManager

Comment 7

[paitken]

I upgraded mozilla 1.7.5 to 1.7.6, and also upgraded my VPN client (Cisco
Systems VPN Client) from 4.6.00.0044 to 4.6.02.0030 at the same time, and
haven't seen this problem since.