Closed Bug 630206 Opened 13 years ago Closed 13 years ago

mail folder after exceeding 4GB limit problems

Categories

(SeaMonkey :: General, defect)

x86
Windows XP
defect
Not set
major

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 462665

People

(Reporter: zetka, Unassigned)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.16) Gecko/20101123 SeaMonkey/2.0.11
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.16) Gecko/20101123 SeaMonkey/2.0.11

After exceeding a certain limit of folder size Sent (about 4.1GB) strange things happens:
1) the folder size incorrectly displayed 8MB (!!!!?) maybe some overload remain..
2) the folder mails could be displayed, but the folder can not be compacted, even after moving a bunch of emails away
3) there was NO WARNING that the folder size was exceeding the limit.
4) using NTFS file system. The folder could not be deleted from sea monkey as well, giving error that Trash exceeds limit.

The way how I resolved it was to make a copy of mails from the "non-compactable" folder to new folder, after that the "natural compacting" was done and after that manualy inside the folder the filenames were changed.

A realy bad problem. The similar problem got before too in other folder, the reason was the same - exceeding the size of folder over 4GB.

Reproducible: Always

Steps to Reproduce:
1. as above - exceed the mail folder size above 4GB
2. see what happens
3.
Actual Results:  
folder could not be compacted or deleted, wrong size.

Expected Results:  
should work without problem. The limit 4G should be increased.
Status: UNCONFIRMED → RESOLVED
Closed: 13 years ago
Resolution: --- → DUPLICATE
(In reply to comment #1)
> 
> *** This bug has been marked as a duplicate of bug 462665 ***

I would like to stress, that now it concerns the Sea Monkey (too), all the bugs described were mostly concerning Thunderbird.
Regards,
It affects both and bug 462665 is in mailnews:Core
You need to log in before you can comment on or make changes to this bug.