106840 - Saving (File > Save As > File, Cmd-S) an email results in an empty file.

Status: RESOLVED WORKSFORME

(SeaMonkey :: MailNews: Message Display, defect)

Description

[Adam Masri]

Platform: PowerBook G3/300/192Mb/48Gb, MacOS X 10.1 + Security Update
Fizzilla Build: 2001101905

Saving an email results in an empty file. Try the following.

1) Run Fizzilla.

2) Open email.

3) Choose a message from your Inbox.

4) Hit Cmd-S or File > Save As > File.

5) Use default name, or name as you wish.

6) Open the resulting file in a text editor (TextEdit, BBEdit, etc).

What happens: the file is empty.

What should happen: the file should have saved the contents of the email mesage.

- Adam

Comment 1

[selmer (gone)]

I'm experiencing this problem on NT w/ build 3/4 09.  Everything looks like it
worked until you notice the file has zero length :-(

Comment 2

[selmer (gone)]

Adding Scott to the CC.  I haven't changed the markings on the bug, not sure if
you think this is the right place for this.

Comment 3

[scottputterman]

Steve, was this happening when you saved the email or when saving an attachment
or both?

Comment 4

[selmer (gone)]

I only manipulated the attachments by doing save as and open then using the
browser save as.  In each case it left me with a 0 byte file.

Here's the bad news: same build, different day, can't dup anymore :-(  I went
back and tried the save as again and suddenly I'm getting the full file stored.
 It's the same emails...

Comment 5

[Olli Männistö]

I have the same problem with W2k and NT4 (.99, .98). You can have your very own
infinite attachment compression with Windows, too.

I'm using IMAP server if it makes any difference. Often nothing happens when I
hit "save attachment", if I keep clicking it, I get a 0-byte file that mozilla
leaves open. Yech.

Comment 6

[Michael Vincenc]

I can duplicate this problem with Mozilla 0.9.9 build 2002031005 and Mozilla
0.9.9+ build 20020415nn (whatever 'nn' might be today; I forgot).

So far, I've only been able to duplicate the problem on my Mac OS X 10.1.3 box
at home.  I tried to duplicate the problem on my Mac OS X 10.1.3 box at work,
and cannot.

One thing to note: The Mac OS X box at work didn't have the latest set of
security patches from Apple via Mac OS X Software Update, "Security Update April
2002".  I just remembered--just now, now that I'm at home--so I can't test the
Mac OS X box at work.

On the other hand, this bug is sufficiently old, so the Security Update April
2002 patches probably don't make a difference.

!mv

Comment 7

[OstGote!]

Is this still an issue with current builds? Otherwise please resolve it as
WORKSFORME.

Comment 8

[Stefan [:stefanh]]

This worksforme with Mozilla 2004041708 on Mac OS 10.2.8. --> wfm.

If anyone can repro the issue with a current build - please reopen.