Markus Brueckner wrote: > > ------------------------------------------------------------------------ > > Subject: > > Mozilla destroyed all mails > From: > > Markus Brueckner <[EMAIL PROTECTED]> > Date: > > Fri, 21 Dec 2001 13:14:32 +0100 > > Newsgroups: > > netscape.public.mozilla.mail-news > > > Hi there, > > 2 days ago I had some kind of accident with my Mozilla 0.9.6 under > Windows. I'm reading the linux-kernel mailing list and use a message > filter to automatically put all Mails in a seperate folder. It worked ok > for me all the time. Until then I collected about 12,000 EMails in this > folder (yes, the list is high traffic). Then I accidently dragged the > folder as a subfolder of a subfolder of a self-created folder. I dragged > it back but all my mails where lost. The thing is that Mozilla didn't > seem to delete them. No unusal disk activity. I looked at the files > where the mails are stored and it's only 133 kb in size. If you guys > didn't invent some kind of super-compressiion, this should be much to > small. > Is this problem in any kind known? Ok, it was only the kernel list this > time and I wasn't able to reproduce the error but if it happens again it > could be necessary mails. I didn't find a bug on bugzilla and didn't > want to file one until I'm able to reproduce it. > My proposal would be that Mozilla tried to copy the folder file. As this > one was big it took some time to copy. But in the meantime I corrected > the position and dragged the folder back. Perhaps then Mozilla began to > copy the file back, not having written it fully yet and therefor messed > it up? Only guessing but I experienced a similar thing with my on code > sometime. > Can anyone even verify the problem? > > Thx in advance > Markus > P.S.: My system is Win2k, Mozilla 0.9.6 >
sounds like the bookmark outliner problem we see.. when moving bookmark folders between folders, stuff is lost.. Yes, copy has to have a change to complete, also you should probably tried to close the compose window before trying to copy back. It could be the db is still open and when you tried to do some fast action it may not have finish writing to the db. If you know about db's, every action performed has to be completed before a new one can work, and it needs to be completed before closing the window.. else I bet what you saw is that it failed to finish. -dman84 -dman84
