89331 - MIME attachment are sent corrupted

Status: VERIFIED DUPLICATE of bug 102536

(MailNews Core :: MIME, defect)

Description

[liebich]

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.2) Gecko/20010628
BuildID:    2001062815

when sending emails with attachments (as MIME) they are often sent currupted. It
can be checked by opening the attachment from the sent folder (klick e.g. on a
zip attachment, winzip reports "corrupt attachment"). Receiver of the message
complain about the same.

Reproducible: Sometimes
Steps to Reproduce:
1. send again
2. 
3.

Problem - can't really reproduce, however my scores are that 25% of all emails
with attachment are sent with corrupt attachments. It seems that the likeliness
of the error increases with the size of the attachment.

Actual Results:  The attachment is corrupt - i.e. it can not be read by the
receiver and not be opened again from the sent folder.

Expected Results:  attachments to be transmitted fine.

seldom already the mail server of the receiver reports an invalid MIME, like in:

------- Failure Reasons  --------

MIME decoding error


and the last mime lines are:

oooAKKKKACiiigAooooAKKKKACiiigAooooAKKKKACiiigAooooAKKKKACiiigAooooAKKKK
ACiiigAooooAKKKKACiiigAooooAKKKKACiiigAooooAKKKKACiiigAooooAKKKKACiiigD/
2Q==
--------------000307090406090305050703--

Comment 1

[Cormac F]

Correcting minor error in bug summary.

Old summary - MIME attachment are sent currupted

New  - MIME attachment are sent corrupted

sorry for the spam!

Comment 2

[Boris Zbarsky [:bzbarsky]]

reporter, are you still seeing this in recent builds?  Please comment; if you are 
this bug should be escalated a bit... :)

If you _are_ seeing this, could you attach a corrupt message to this bug using 
http://bugzilla.mozilla.org/createattachment.cgi?id=89331 ?

Comment 3

[Asa Dotzler [:asa]]

setting bug status to New

Comment 4

[liebich]

Attachment: example of a corrupt mime attachment

Comment 5

[Boris Zbarsky [:bzbarsky]]

Attachment: Actual message from zipfile as text/plain

Comment 6

[Boris Zbarsky [:bzbarsky]]

Attachment: reply sent by receiving server notifying of corruption

Comment 7

[Boris Zbarsky [:bzbarsky]]

I tried looking at the attachment in that mail file.  Once I replaced CRLF with
LF throughout (I'm on Unix), I could get the attachment out of the mail with no
problems.  But the PDF file was corrupt according to acroread.

Comment 8

[Ashley Bischoff (blog at handcoding.com)]

*** Bug 94868 has been marked as a duplicate of this bug. ***

Comment 9

[Ashley Bischoff (blog at handcoding.com)]

See also additional testcases in bug 94868.

Comment 10

[liebich]

Attachment: Original file attachment, see next attachment on how it got corrupt

Comment 11

[liebich]

Attachment: Sent file - got corrupted / taken from Sent folder

Comment 12

[liebich]

Attachment: Rejected email - MIME error (refers to previous attachment)

Comment 13

[Geoff Gustafson]

This does sound like the same bug that I gave a patch for in bug 102536. That 
only happens when the mail w/ attachment is sent offline, then 'sent later', 
which hasn't been specified here, however.

In that bug I explain why the likelihood scales with attachment size. That 
would predict that attachments of about 92K would fail 25% of the time. One 
user may be able to reproduce it consistently with a certain attachment, but 
another won't see it because their message headers is longer or shorter 
(different email address, etc.) changing where the 4K buffer divisions fall.

The result of the bug is that one character from the beginning of an encoded 
line gets deleted, thus the decoding will fail.

Comment 14

[liebich]

as the original reporter I want to add to the last message from Geoff, yes the
description of 102536 sounds very much as I have observed - small attachment
(<50 kB) never got corrupt, big ones (>1MB) very often - in between with
increasing likeliness.

As I work with dial-in internet connection, those messages were "send later",
however I recall that I tested it as well online (and it would fail). Maybe best
to leave the bug open until we get the version with the 102536 fix (is it
0.9.7?) and test that with "send now" large attachments.

Comment 15

[scottputterman]

liebich, could you try downloading a daily build to see if this works for you now?

Comment 16

[liebich]

I made some checks with 0.9.6 (2001112009) both "send" and "send later", I could
only reproduce the error went using "send later" - which would support Geoffs
comment #13. Please make this bug a doublicate of 102536, which now had been solved.

*** This bug has been marked as a duplicate of 102536 ***

Comment 17

[[e-mail] (gone - use [e-mail] instead)]

verified dup.