107314 - Attachments in IMAP INBOX are corrupt after using offline mode

Status: VERIFIED DUPLICATE of bug 110067

(SeaMonkey :: MailNews: Backend, defect)

Description

[Sven Hazejager]

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

Attachments in a mailbox that has been synchronized for offline use are corrupt.
Even new e-mails that have not yet been synchronized produce corrupt attachments
(all attachments are 27 bytes long).


Reproducible: Always
Steps to Reproduce:
Mozilla worked just fine until I used the offline mode function. I synchronized
the mailbox (including all attachments, since the file size limit was not set)
and I could still open attachments. After going online, suddenly, all the
attachments in Mozilla are cut off at 27 bytes. This applies to old mail (mail
that was synchronized) and new mail coming in. I've tried to delete the local
files INBOX and INBOX.msf, but it didn't help. Now, I cannot open any
attachments in Mozilla in my Inbox.
However: if I copy the mail with attachments to another IMAP folder that was NOT
synchronized, I can open the attachments correctly!

Actual Results:  Attachments are 27 bytes long. "Open" and "Save as" do the same.

Expected Results:  Correctly open the attachments.

This is what Mozilla writes to the log when INCORRECTLY opening the mail:

464[217e7c8]: proxy:S-INBOX:STREAM:OPEN Size: 4600: Begin Message Download Stream
464[217e7c8]: proxy:S-INBOX:CreateNewLineFromSocket: Return-Path:
<[e-mail]>

464[217e7c8]: proxy:S-INBOX:CreateNewLineFromSocket: Received: from
pop3.demon.nl (localhost.chain.loc [127.0.0.1])

464[217e7c8]: proxy:S-INBOX:CreateNewLineFromSocket: 	by chain.demon.nl
(8.11.6/8.11.6) with ESMTP id f9SD6KE20181

464[217e7c8]: proxy:S-INBOX:CreateNewLineFromSocket: 	for <[e-mail]>;
Sun, 28 Oct 2001 14:06:20 +0100 (CET)

464[217e7c8]: proxy:S-INBOX:CreateNewLineFromSocket: 	(envelope-from
[e-mail])

464[217e7c8]: proxy:S-INBOX:CreateNewLineFromSocket: Received: from
punt-14.mail.nl.demon.net by mailstore for [e-mail]

464[217e7c8]: proxy:S-INBOX:CreateNewLineFromSocket:           id
1004273966:14:03472:0; Sun, 28 Oct 2001 12:59:26 GMT

464[217e7c8]: proxy:S-INBOX:CreateNewLineFromSocket: Received: from
post-11.mail.nl.demon.net ([194.159.73.21])

464[217e7c8]: proxy:S-INBOX:CreateNewLineFromSocket:           by
punt-14.mail.nl.demon.net  id aa1403429; 28 Oct 2001 12:59 GMT

464[217e7c8]: proxy:S-INBOX:CreateNewLineFromSocket: Received: from
[212.238.65.196] (helo=ton)

464[217e7c8]: proxy:S-INBOX:CreateNewLineFromSocket: 	by post.mail.nl.demon.net
with smtp (Exim 3.33 #1)

464[217e7c8]: proxy:S-INBOX:CreateNewLineFromSocket: 	id 15xpWt-000Jf0-00; Sun, 28
Oct 2001 12:59:07 +0000

464[217e7c8]: proxy:S-INBOX:CreateNewLineFromSocket: From: "Ton van Rooijen"
<[e-mail]>

464[217e7c8]: proxy:S-INBOX:CreateNewLineFromSocket: To: "Sven Hazejager"
<[e-mail]>

464[217e7c8]: proxy:S-INBOX:CreateNewLineFromSocket: Cc: "Rene Hazejager"
<[e-mail]>

464[217e7c8]: proxy:S-INBOX:CreateNewLineFromSocket: Subject: veslaving 
gebruikers en ICT..........

464[217e7c8]: proxy:S-INBOX:CreateNewLineFromSocket: Date: Sun, 28 Oct 2001
15:02:24 +0100

464[217e7c8]: proxy:S-INBOX:CreateNewLineFromSocket: Message-ID:
<002901c15fb9$2b5035f0$0100000a@ton>

464[217e7c8]: proxy:S-INBOX:CreateNewLineFromSocket: MIME-Version: 1.0

464[217e7c8]: proxy:S-INBOX:CreateNewLineFromSocket: Content-Type: multipart/mixed;

464[217e7c8]: proxy:S-INBOX:CreateNewLineFromSocket: 
boundary="----=_NextPart_000_002A_01C15FC1.8D149DF0"

464[217e7c8]: proxy:S-INBOX:CreateNewLineFromSocket: X-Priority: 3 (Normal)

464[217e7c8]: proxy:S-INBOX:CreateNewLineFromSocket: X-MSMail-Priority: Normal

464[217e7c8]: proxy:S-INBOX:CreateNewLineFromSocket: X-Mailer: Microsoft Outlook
8.5, Build 4.71.2232.26

464[217e7c8]: proxy:S-INBOX:CreateNewLineFromSocket: Importance: Normal

464[217e7c8]: proxy:S-INBOX:CreateNewLineFromSocket: X-MimeOLE: Produced By
Microsoft MimeOLE V4.72.2106.4

464[217e7c8]: proxy:S-INBOX:CreateNewLineFromSocket: 

464[217e7c8]: proxy:S-INBOX:CreateNewLineFromSocket:  BODY[1.MIME] {85}

464[217e7c8]: proxy:S-INBOX:CreateNewLineFromSocket: Content-Type: text/plain;

464[217e7c8]: proxy:S-INBOX:CreateNewLineFromSocket: 	charset="iso-8859-1"

464[217e7c8]: proxy:S-INBOX:CreateNewLineFromSocket: Content-Transfer-Encoding: 7bit

464[217e7c8]: proxy:S-INBOX:CreateNewLineFromSocket: 

464[217e7c8]: proxy:S-INBOX:CreateNewLineFromSocket:  BODY[2.MIME] {176}

464[217e7c8]: proxy:S-INBOX:CreateNewLineFromSocket: Content-Type:
application/msword;

464[217e7c8]: proxy:S-INBOX:CreateNewLineFromSocket: 	name="verslaving 2 200901.doc"

464[217e7c8]: proxy:S-INBOX:CreateNewLineFromSocket: Content-Transfer-Encoding:
base64

464[217e7c8]: proxy:S-INBOX:CreateNewLineFromSocket: Content-Disposition:
attachment;

464[217e7c8]: proxy:S-INBOX:CreateNewLineFromSocket: 	filename="verslaving 2
200901.doc"

464[217e7c8]: proxy:S-INBOX:CreateNewLineFromSocket: 

464[217e7c8]: proxy:S-INBOX:CreateNewLineFromSocket:  BODY[3.MIME] {202}

464[217e7c8]: proxy:S-INBOX:CreateNewLineFromSocket: Content-Type:
application/msword;

464[217e7c8]: proxy:S-INBOX:CreateNewLineFromSocket: 
name="ColumnCOMMgewoonautomatiseerders.doc"

464[217e7c8]: proxy:S-INBOX:CreateNewLineFromSocket: Content-Transfer-Encoding:
base64

464[217e7c8]: proxy:S-INBOX:CreateNewLineFromSocket: Content-Disposition:
attachment;

464[217e7c8]: proxy:S-INBOX:CreateNewLineFromSocket: 
filename="ColumnCOMMgewoonautomatiseerders.doc"

464[217e7c8]: proxy:S-INBOX:CreateNewLineFromSocket: 

464[217e7c8]: proxy:S-INBOX:CreateNewLineFromSocket: )

464[217e7c8]: proxy:S-INBOX:CreateNewLineFromSocket: 25 OK UID FETCH completed

464[217e7c8]: proxy:S-INBOX:STREAM:OPEN Size: 2090: Begin Message Download Stream
464[217e7c8]: proxy:S-INBOX:SHELL:GENERATE-MessageRFC822: 0
464[217e7c8]: proxy:S-INBOX:SHELL:GENERATE-MessageHeaders: 0
464[217e7c8]: proxy:S-INBOX:SHELL:GENERATE-Part-Prefetched: 0
464[217e7c8]: proxy:S-INBOX:SHELL:GENERATE-Multipart: 0
464[217e7c8]: proxy:S-INBOX:SHELL:GENERATE-Boundary: 0
464[217e7c8]: proxy:S-INBOX:SHELL:GENERATE-Leaf: 1
464[217e7c8]: proxy:S-INBOX:SHELL:GENERATE-MIMEHeader: 1
464[217e7c8]: proxy:S-INBOX:SHELL:GENERATE-Part-Inline: 1
464[217e7c8]: proxy:S-INBOX:SendData: 26 UID fetch 42523 (BODY[1])

464[217e7c8]: proxy:S-INBOX:CreateNewLineFromSocket: * 902 FETCH (UID 42523
BODY[1] {37}

464[217e7c8]: proxy:S-INBOX:CreateNewLineFromSocket: Sven 

464[217e7c8]: proxy:S-INBOX:CreateNewLineFromSocket: 

464[217e7c8]: proxy:S-INBOX:CreateNewLineFromSocket: Was ik nog vergeten. 

464[217e7c8]: proxy:S-INBOX:CreateNewLineFromSocket: 

464[217e7c8]: proxy:S-INBOX:CreateNewLineFromSocket: Ton)

464[217e7c8]: proxy:S-INBOX:CreateNewLineFromSocket: 26 OK UID FETCH completed


This is what happens if I copy the mail to another folder and open it:


528[316e8d8]: proxy:S-mail/FreeBSD:STREAM:OPEN Size: 53172: Begin Message
Download Stream
528[316e8d8]: proxy:S-mail/FreeBSD:CreateNewLineFromSocket: From: "Ton van
Rooijen" <[e-mail]>

528[316e8d8]: proxy:S-mail/FreeBSD:CreateNewLineFromSocket: To: "Sven Hazejager"
<[e-mail]>

528[316e8d8]: proxy:S-mail/FreeBSD:CreateNewLineFromSocket: Cc: "Rene Hazejager"
<[e-mail]>

528[316e8d8]: proxy:S-mail/FreeBSD:CreateNewLineFromSocket: Subject: veslaving 
gebruikers en ICT..........

528[316e8d8]: proxy:S-mail/FreeBSD:CreateNewLineFromSocket: Date: Sun, 28 Oct
2001 15:02:24 +0100

528[316e8d8]: proxy:S-mail/FreeBSD:CreateNewLineFromSocket: Message-ID:
<002901c15fb9$2b5035f0$0100000a@ton>

528[316e8d8]: proxy:S-mail/FreeBSD:CreateNewLineFromSocket: X-Priority: 3 (Normal)

528[316e8d8]: proxy:S-mail/FreeBSD:CreateNewLineFromSocket: 

528[316e8d8]: proxy:S-mail/FreeBSD:CreateNewLineFromSocket: )

528[316e8d8]: proxy:S-mail/FreeBSD:STREAM:CLOSE: Normal Message End Download Stream
528[316e8d8]: proxy:S-mail/FreeBSD:CreateNewLineFromSocket: 15 OK UID FETCH
completed

528[316e8d8]: proxy:S-mail/FreeBSD:SendData: 16 UID fetch 15187 (BODYSTRUCTURE)

528[316e8d8]: proxy:S-mail/FreeBSD:CreateNewLineFromSocket: * 2325 FETCH (UID
15187 BODYSTRUCTURE (("TEXT" "PLAIN" ("CHARSET" "iso-8859-1") NIL NIL "7BIT" 37
4 NIL NIL NIL)("APPLICATION" "MSWORD" ("NAME" "verslaving 2 200901.doc") NIL NIL
"BASE64" 21722 NIL ("ATTACHMENT" ("FILENAME" "verslaving 2 200901.doc"))
NIL)("APPLICATION" "MSWORD" ("NAME" "ColumnCOMMgewoonautomatiseerders.doc") NIL
NIL "BASE64" 29428 NIL ("ATTACHMENT" ("FILENAME"
"ColumnCOMMgewoonautomatiseerders.doc")) NIL) "MIXED" ("BOUNDARY" "-
528[316e8d8]: proxy:S-mail/FreeBSD:CreateNewLineFromSocket: 16 OK UID FETCH
completed

528[316e8d8]: proxy:S-mail/FreeBSD:SendData: 17 UID fetch 15187 (BODY[HEADER]
BODY[1.MIME] BODY[2.MIME] BODY[3.MIME])

528[316e8d8]: proxy:S-mail/FreeBSD:CreateNewLineFromSocket: * 2325 FETCH (UID
15187 BODY[HEADER] {1284}

528[316e8d8]: proxy:S-mail/FreeBSD:STREAM:OPEN Size: 53172: Begin Message
Download Stream
528[316e8d8]: proxy:S-mail/FreeBSD:CreateNewLineFromSocket: Return-Path:
<[e-mail]>

528[316e8d8]: proxy:S-mail/FreeBSD:CreateNewLineFromSocket: Received: from
pop3.demon.nl (localhost.chain.loc [127.0.0.1])

528[316e8d8]: proxy:S-mail/FreeBSD:CreateNewLineFromSocket: 	by chain.demon.nl
(8.11.6/8.11.6) with ESMTP id f9SD6KE20181

528[316e8d8]: proxy:S-mail/FreeBSD:CreateNewLineFromSocket: 	for
<[e-mail]>; Sun, 28 Oct 2001 14:06:20 +0100 (CET)

528[316e8d8]: proxy:S-mail/FreeBSD:CreateNewLineFromSocket: 	(envelope-from
[e-mail])

528[316e8d8]: proxy:S-mail/FreeBSD:CreateNewLineFromSocket: Received: from
punt-14.mail.nl.demon.net by mailstore for [e-mail]

528[316e8d8]: proxy:S-mail/FreeBSD:CreateNewLineFromSocket:           id
1004273966:14:03472:0; Sun, 28 Oct 2001 12:59:26 GMT

528[316e8d8]: proxy:S-mail/FreeBSD:CreateNewLineFromSocket: Received: from
post-11.mail.nl.demon.net ([194.159.73.21])

528[316e8d8]: proxy:S-mail/FreeBSD:CreateNewLineFromSocket:           by
punt-14.mail.nl.demon.net  id aa1403429; 28 Oct 2001 12:59 GMT

528[316e8d8]: proxy:S-mail/FreeBSD:CreateNewLineFromSocket: Received: from
[212.238.65.196] (helo=ton)

528[316e8d8]: proxy:S-mail/FreeBSD:CreateNewLineFromSocket: 	by
post.mail.nl.demon.net with smtp (Exim 3.33 #1)

528[316e8d8]: proxy:S-mail/FreeBSD:CreateNewLineFromSocket: 	id 15xpWt-000Jf0-00;
Sun, 28 Oct 2001 12:59:07 +0000

528[316e8d8]: proxy:S-mail/FreeBSD:CreateNewLineFromSocket: From: "Ton van
Rooijen" <[e-mail]>

528[316e8d8]: proxy:S-mail/FreeBSD:CreateNewLineFromSocket: To: "Sven Hazejager"
<[e-mail]>

528[316e8d8]: proxy:S-mail/FreeBSD:CreateNewLineFromSocket: Cc: "Rene Hazejager"
<[e-mail]>

528[316e8d8]: proxy:S-mail/FreeBSD:CreateNewLineFromSocket: Subject: veslaving 
gebruikers en ICT..........

528[316e8d8]: proxy:S-mail/FreeBSD:CreateNewLineFromSocket: Date: Sun, 28 Oct
2001 15:02:24 +0100

528[316e8d8]: proxy:S-mail/FreeBSD:CreateNewLineFromSocket: Message-ID:
<002901c15fb9$2b5035f0$0100000a@ton>

528[316e8d8]: proxy:S-mail/FreeBSD:CreateNewLineFromSocket: MIME-Version: 1.0

528[316e8d8]: proxy:S-mail/FreeBSD:CreateNewLineFromSocket: Content-Type:
multipart/mixed;

528[316e8d8]: proxy:S-mail/FreeBSD:CreateNewLineFromSocket: 
boundary="----=_NextPart_000_002A_01C15FC1.8D149DF0"

528[316e8d8]: proxy:S-mail/FreeBSD:CreateNewLineFromSocket: X-Priority: 3 (Normal)

528[316e8d8]: proxy:S-mail/FreeBSD:CreateNewLineFromSocket: X-MSMail-Priority:
Normal

528[316e8d8]: proxy:S-mail/FreeBSD:CreateNewLineFromSocket: X-Mailer: Microsoft
Outlook 8.5, Build 4.71.2232.26

528[316e8d8]: proxy:S-mail/FreeBSD:CreateNewLineFromSocket: Importance: Normal

528[316e8d8]: proxy:S-mail/FreeBSD:CreateNewLineFromSocket: X-MimeOLE: Produced
By Microsoft MimeOLE V4.72.2106.4

528[316e8d8]: proxy:S-mail/FreeBSD:CreateNewLineFromSocket: 

528[316e8d8]: proxy:S-mail/FreeBSD:CreateNewLineFromSocket:  BODY[1.MIME] {85}

528[316e8d8]: proxy:S-mail/FreeBSD:CreateNewLineFromSocket: Content-Type:
text/plain;

528[316e8d8]: proxy:S-mail/FreeBSD:CreateNewLineFromSocket: 	charset="iso-8859-1"

528[316e8d8]: proxy:S-mail/FreeBSD:CreateNewLineFromSocket:
Content-Transfer-Encoding: 7bit

528[316e8d8]: proxy:S-mail/FreeBSD:CreateNewLineFromSocket: 

528[316e8d8]: proxy:S-mail/FreeBSD:CreateNewLineFromSocket:  BODY[2.MIME] {176}

528[316e8d8]: proxy:S-mail/FreeBSD:CreateNewLineFromSocket: Content-Type:
application/msword;

528[316e8d8]: proxy:S-mail/FreeBSD:CreateNewLineFromSocket: 	name="verslaving 2
200901.doc"

528[316e8d8]: proxy:S-mail/FreeBSD:CreateNewLineFromSocket:
Content-Transfer-Encoding: base64

528[316e8d8]: proxy:S-mail/FreeBSD:CreateNewLineFromSocket: Content-Disposition:
attachment;

528[316e8d8]: proxy:S-mail/FreeBSD:CreateNewLineFromSocket: 	filename="verslaving
2 200901.doc"

528[316e8d8]: proxy:S-mail/FreeBSD:CreateNewLineFromSocket: 

528[316e8d8]: proxy:S-mail/FreeBSD:CreateNewLineFromSocket:  BODY[3.MIME] {202}

528[316e8d8]: proxy:S-mail/FreeBSD:CreateNewLineFromSocket: Content-Type:
application/msword;

528[316e8d8]: proxy:S-mail/FreeBSD:CreateNewLineFromSocket: 
name="ColumnCOMMgewoonautomatiseerders.doc"

528[316e8d8]: proxy:S-mail/FreeBSD:CreateNewLineFromSocket:
Content-Transfer-Encoding: base64

528[316e8d8]: proxy:S-mail/FreeBSD:CreateNewLineFromSocket: Content-Disposition:
attachment;

528[316e8d8]: proxy:S-mail/FreeBSD:CreateNewLineFromSocket: 
filename="ColumnCOMMgewoonautomatiseerders.doc"

528[316e8d8]: proxy:S-mail/FreeBSD:CreateNewLineFromSocket: 

528[316e8d8]: proxy:S-mail/FreeBSD:CreateNewLineFromSocket: )

528[316e8d8]: proxy:S-mail/FreeBSD:CreateNewLineFromSocket: 17 OK UID FETCH
completed

528[316e8d8]: proxy:S-mail/FreeBSD:STREAM:OPEN Size: 2090: Begin Message
Download Stream
528[316e8d8]: proxy:S-mail/FreeBSD:SHELL:GENERATE-MessageRFC822: 0
528[316e8d8]: proxy:S-mail/FreeBSD:SHELL:GENERATE-MessageHeaders: 0
528[316e8d8]: proxy:S-mail/FreeBSD:SHELL:GENERATE-Part-Prefetched: 0
528[316e8d8]: proxy:S-mail/FreeBSD:SHELL:GENERATE-Multipart: 0
528[316e8d8]: proxy:S-mail/FreeBSD:SHELL:GENERATE-Boundary: 0
528[316e8d8]: proxy:S-mail/FreeBSD:SHELL:GENERATE-Leaf: 1
528[316e8d8]: proxy:S-mail/FreeBSD:SHELL:GENERATE-MIMEHeader: 1
528[316e8d8]: proxy:S-mail/FreeBSD:SHELL:GENERATE-Part-Inline: 1
528[316e8d8]: proxy:S-mail/FreeBSD:SendData: 18 UID fetch 15187 (BODY[1])

528[316e8d8]: proxy:S-mail/FreeBSD:CreateNewLineFromSocket: * 2325 FETCH (UID
15187 BODY[1] {37}

528[316e8d8]: proxy:S-mail/FreeBSD:CreateNewLineFromSocket: Sven 

528[316e8d8]: proxy:S-mail/FreeBSD:CreateNewLineFromSocket: 

528[316e8d8]: proxy:S-mail/FreeBSD:CreateNewLineFromSocket: Was ik nog vergeten. 

528[316e8d8]: proxy:S-mail/FreeBSD:CreateNewLineFromSocket: 

528[316e8d8]: proxy:S-mail/FreeBSD:CreateNewLineFromSocket: Ton)

528[316e8d8]: proxy:S-mail/FreeBSD:CreateNewLineFromSocket: 18 OK UID FETCH
completed

528[316e8d8]: proxy:S-mail/FreeBSD:SHELL:GENERATE-Boundary: 0
528[316e8d8]: proxy:S-mail/FreeBSD:SHELL:GENERATE-Leaf: 2
528[316e8d8]: proxy:S-mail/FreeBSD:SHELL:GENERATE-XHeader: 2
528[316e8d8]: proxy:S-mail/FreeBSD:SHELL:GENERATE-MIMEHeader: 2
528[316e8d8]: proxy:S-mail/FreeBSD:SHELL:GENERATE-Filling: 2
528[316e8d8]: proxy:S-mail/FreeBSD:SHELL:GENERATE-Boundary: 0
528[316e8d8]: proxy:S-mail/FreeBSD:SHELL:GENERATE-Leaf: 3
528[316e8d8]: proxy:S-mail/FreeBSD:SHELL:GENERATE-XHeader: 3
528[316e8d8]: proxy:S-mail/FreeBSD:SHELL:GENERATE-MIMEHeader: 3
528[316e8d8]: proxy:S-mail/FreeBSD:SHELL:GENERATE-Filling: 3
528[316e8d8]: proxy:S-mail/FreeBSD:SHELL:GENERATE-Boundary-Last: 0
528[316e8d8]: proxy:S-mail/FreeBSD:STREAM:CLOSE: Normal Message End Download Stream
528[316e8d8]: BODYSHELL:  Adding shell to cache.
528[316e8d8]: proxy:S-mail/FreeBSD:SHELL: Loading Part, using cached shell.
528[316e8d8]: proxy:S-mail/FreeBSD:STREAM:OPEN Size: 31481: Begin Message
Download Stream
528[316e8d8]: proxy:S-mail/FreeBSD:SHELL:GENERATE-MessageRFC822: 0
528[316e8d8]: proxy:S-mail/FreeBSD:SHELL:GENERATE-MessageHeaders: 0
528[316e8d8]: proxy:S-mail/FreeBSD:SHELL:GENERATE-Part-Prefetched: 0
528[316e8d8]: proxy:S-mail/FreeBSD:SHELL:GENERATE-Multipart: 0
528[316e8d8]: proxy:S-mail/FreeBSD:SHELL:GENERATE-Boundary: 0
528[316e8d8]: proxy:S-mail/FreeBSD:SHELL:GENERATE-Leaf: 1
528[316e8d8]: proxy:S-mail/FreeBSD:SHELL:GENERATE-XHeader: 1
528[316e8d8]: proxy:S-mail/FreeBSD:SHELL:GENERATE-MIMEHeader: 1
528[316e8d8]: proxy:S-mail/FreeBSD:SHELL:GENERATE-Filling: 1
528[316e8d8]: proxy:S-mail/FreeBSD:SHELL:GENERATE-Boundary: 0
528[316e8d8]: proxy:S-mail/FreeBSD:SHELL:GENERATE-Leaf: 2
528[316e8d8]: proxy:S-mail/FreeBSD:SHELL:GENERATE-XHeader: 2
528[316e8d8]: proxy:S-mail/FreeBSD:SHELL:GENERATE-MIMEHeader: 2
528[316e8d8]: proxy:S-mail/FreeBSD:SHELL:GENERATE-Filling: 2
528[316e8d8]: proxy:S-mail/FreeBSD:SHELL:GENERATE-Boundary: 0
528[316e8d8]: proxy:S-mail/FreeBSD:SHELL:GENERATE-Leaf: 3
528[316e8d8]: proxy:S-mail/FreeBSD:SHELL:GENERATE-MIMEHeader: 3
528[316e8d8]: proxy:S-mail/FreeBSD:SHELL:GENERATE-Part-Inline: 3
528[316e8d8]: proxy:S-mail/FreeBSD:SendData: 19 UID fetch 15187 (BODY[3])

528[316e8d8]: proxy:S-mail/FreeBSD:CreateNewLineFromSocket: * 2325 FETCH (UID
15187 BODY[3] {29428}

528[316e8d8]: proxy:S-mail/FreeBSD:CreateNewLineFromSocket:
0M8R4KGxGuEAAAAAAAAAAAAAAAAAAAAAPgADAP7/CQAGAAAAAAAAAAAAAAABAAAAJQAAAAAAAAAA

528[316e8d8]: proxy:S-mail/FreeBSD:CreateNewLineFromSocket:
EAAAJwAAAAEAAAD+////AAAAACQAAAD/////////////////////////////////////////////

(and the attachment continues...)

Comment 1

[R.K.Aa.]

something similar was reported in bug 86206.
Added comment in bug 82583 about these both.
Changing component to "offline"

Comment 2

[grylchan]

Reporter can you get a more recent build?

I am using 20011019 build (ie 2001-10-22-18-0.9.4)
on Win NT 4.0 and I can't reproduce the problem.

I have tried downloading different type/sized attachments
(ie word, excel, gif, jpeg, mpeg) and I am able to save them
or open them while online or offline. 

I see you are using a imap mail box and so am I.

This is what I did:

1.I migrated an existing profile
2.Logged into messenger
3.Went to a folder with some known attachements.
4.Opened them/saved them while online. No problems.
5.Brought up the Download and Sync window
6.Selected that folder for downloading.
7.Downloaded that folder and then went offline
8.Open the downloaded mesgs with attachements. No problems.
9.Saved the attachments and tried to open them. No problems.
10.Went back online.
11.Retried opening and saving the attachments. No problems.

Am I missing a step? Can you try a more recent build?

Comment 3

[grylchan]

Also the size of the files did not change when i downloaded
them. The size of the files I used varied (3777kb, 11kb, 60kb,
42 kb)

Comment 4

[Sven Hazejager]

I've just tried the following.

1. With Mozilla not running, delete ImapMail and Cache folders
2. Attachments work again in online mode
3. Go offline with full synchronization
4. Attachments work
5. Go online again
6. Attachments work
7. Close Mozilla
8. Open Mozilla
9. Attachments do not work anymore

Doing above things a second time however do not help! Now my Mozilla is broken
again. I will try a more recent build (I am now using the 0.9.5 release version)
tomorrow.

Comment 5

[Sven Hazejager]

I've narrowed the problem down a bit. If INBOX is selected in Account
Settings->Offline&Disk Space->Select..., a file INBOX is created (along with the
INBOX.msf that already is there) in my profile directory\ImapMail. That file is
8kb long. After restarting Mozilla, all e-mails with attachments do not work
anymore. Note that I have NOT synchronized NOR have I gone offline. I've been
online all the time, but I've selected INBOX in the Select... menu.
Now if I delete only the INBOX file (after closing Mozilla) and I open Mozilla,
normal emails are displayed correctly (as they have all along), but emails with
attachments are simply blank. I have to delete the entire ImapMail directory AND
make sure that INBOX is not selected to have Mozilla read attachments correctly.

I hope you guys can reproduce this one...

Comment 6

[grylchan]

Ok this is what I am seeing using the commercial
trunk build 2001-10-26-09-trunk/ NT 4.0

1.Login to imap mail act
2.I have two mesgs (one with a word file, other excel) in my inbox
3.I double click on each attachment and it opens up
  properly in word/excel.
4.I now go to Edit|Preferences|Mail&Newsgrp Account Settings
  offline&Diskspace| and click on select button.
5.I select the inbox for download and click ok, ok.
6.WithOUT clicking on the inbox again, I quit the browser entirely. 
  (dont have it running at all)
7.I start browser, then messenger, and login to my mail acct.
8.I now go to the 2 mesgs with excel/word attachs.
9.I double click on word file:
  -i select open it with word then mesg appears:
  "Microsoft Word can't import specified format. The feature
   is not installed. Would you like to install now?"
  I click no and word file comes up with garbage.
10. I double click on excel file:
   -I select open the file in excel
   -mesg appears
    "This file is not in a recognizable format"
   -I click ok and see garbage in excel file
11.If i try to do a 'save as' on the attachements
   they are saved but the size is only 1kb and 
   when I try opening I get the same error mesg
12.I have the exact same mesgs saved in another folder (not selected
   for download)
13.I repeat step 9 and 10 and no problem opening either file.

If I do a 'download and sync' on the other folder with word/excel
attachs, after they have been downloaded, I can double click on
either file and it opens up properly.

Reporter I don't see your 2nd inbox file you are talking about.


   

Comment 7

[grylchan]

Investigating some more..using 2001-10-26-09-trunk build.

I think I have found the problem. It's very tricky and
only involves this one scenario:
 -attachments like word/excel get corrupted if you do the following:
  1.Make sure you have a word/excel attachment in a mail mesg in your inbox
    already
  2.Login to messenger and select the inbox
  3.Go to Edit|Preferences|Mail&Newsgrp Account Settings|Offline & Diskspace
  4.Click select button
  5.Check the inbox in Items for Offline Use window
  6.Click ok, ok.
  7.Select a mesg in the inbox with the word/excel attachment.
  8.Double click on attach icon in attachment window
  9.Window pops up asking you if you want to open or save
    -Choose open
      -it will say "Microsoft Word can't import specified format. 
      -and you will see the file is corrupted when opened
    -Choose save
      -the file will only be 1kb in size
      -and opening it will result in same error mesg listed above
  10.If that doesn't work.Quit the entire application and restart.
  11.Then try opening one of the files and you should get the error mesg
  12.You can also see this problem by bringing up the property 
     window for a particular folder, click offline tab, and check
     the box that says 'select the folder for offline use'. Do not
     click download now button. Click ok. Then go word/excel attach
     in that folder and try to open it up.

You do not see this problem if you do any of the following:
  -Using Download and Sync process (and click select button and select inbox)
  -Doing a get selected mesg/get flagged mesg
  -Go to Edit|Preferences|Mail&Newsgrp Account Settings|Offline & Diskspace
   Click select button, select inbox, ok, ok, then immediately click offline
   icon and  say yes to download
  -property dialog of the window, offline tab, check
   the box that says 'select the folder for offline use', and click
   download now button.

So in short this is what I think is happening:
 * If you select a folder for offline use in "Items for offline
   Use window" or by using the property window and checking
   the box that says 'select the folder for offline use'. When
   you click on a message, it 'automatically' downloads that
   particular message. But since we haven't downloaded properly
   (either by going offline, download sync window, download now
    button off property window), the attachment gets messed up.
 
David I hope I am clear on this. Please let me know if I babbled
to much. :-)

I also noticed (don't know if relevant) that when you open up
a word/excel document, it doesn't keep the origina1 file name
and instead it has temporary name like "13jd.doc"

Changing status to new.


      
  

Comment 8

[grylchan]

Wanted to add I tested other type of attachments (wav,mp3,vcf)
and had no problems using the steps on 2001-10-29 19:40.
I was able to open or save them and they worked properly and
were not corrupted.

Comment 9

[Navneet Karnani]

I saw this too. But I did not know that this happens only for folders marked for
offline use. Read bug 107755 for details.

- Navneet

Comment 10

[Sven Hazejager]

I've tried to do the same as the tester, but I get other results.
1. Select (not download) INBOX as offline folder. Attachments are corrupted.
2. Download INBOX, stay online. Attachments are corrupted.
3. Go offline. Attachments are corrupted.
4. Go online. Attachments are corrupted.
5. Deselect INBOX. Attachments are corrupted.
6. Delete the entire ImapMail folder stored on disk in the Mozilla User profile
directory.
7. Start Mozilla. Attachments work again.

And another thing. Even if attachments work after downloading, it still is a
gigantic bug. Consider the following. User is online and has synchronized has
mailbox, so that attachments work again. Now a new e-mail comes in with an
attachment. That attachment is corrupted, because it has not yet been
synchronized. The user has to synchronize all the time, just to get his
attachments working...

Thanks for your input anyway guys!

Comment 11

[grylchan]

Reporter:
I agree with you after you do step 1, yes attachments
will be corrupted (after selecting them for download)
if you click on that mesg and try to open/save it. If
after selecting the folder, you download entire
folder, attaches should work fine assuming you have not individually
clicked on a mesg with attachemnt before downloading entire folder.

And yes once the mesg is corrupted it won't work whether you restart, 
do a download and sync, go online/offline, etc...

David, maybe the possible solution is to prevent mesgs from automatically
downloading when you select a mesg while online
(if a folder has been selected for download) until they do a 
  -'download and sync now'
  - click the download button in properties window
  - click 'download' when the download prompt appears after
    clicking offline icon/selecting work offline from the File menu.

I can't figure out why only word/excel/pwrpt files get corrupted while
other file types do not.

Comment 12

[grylchan]

I spoke to soon.

Yes other attached files do get corrupted beside word or excel.
Other file attachements that get corrupted: *.dll, *.pdf, *.zip, *.exe,
I try to save them and they are all 1kb in size.

While other files: *.wav,*.mp3,*.html,*.txt,*.gif,*.jpeg are not
corrupted.

If I try to open the pdf file it says "There was an
error opening this document. File does not begin
with '%PDF-'."

Opening a zip attachment says "Can not open file. It does not appear to
be a valid archive".

Comment 13

[grylchan]

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

Comment 14

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

verified dup