User-Agent: Mozilla/5.0 (rv:220.127.116.11) Gecko/20071022 GNU/Linux Firefox/18.104.22.168
Build Identifier: Version 22.214.171.124 (20071022)
With a recent thread on ML i came again across a problem with Thunderbird
that i had myself 1 or 2 years ago.
Thunderbird uses mailbox files to store mails and an aditionally *.msf file
for meta data of that mbox-file.
Now when you delete a mail in TB it only disappears in the mail pane but is
still physically stored on harddisc in the mbox.
To really delete a mail then s.o. has to "compact" that folder.
New users (or those not interrested in technic) wont notice that and then the
profile folder can become very large.
In the specific thread the OP had mails back from 2005 still in his profile
which had grown up to 2 gig.
2 gig is approximately where we come to filesystem limitations (max size per
Now to prevent that i call for commend on change the default of:
that way a user gets a dialog when the threshold (default is 100kB iirc) is
reached and gets asked to "compact" (read as really physically delete all
previous in TB deleted mails) that folder.
I have searched bugzilla.mozilla.org for bugs like that and coulnd´t find
one. Also on launchpad is no similar bug report it seems.
So i would like to know is it feasible to solve that somehow?
Steps to Reproduce:
1. send lots of mails
2. delete them in Thunderbird
3. check size of profile directory
with default settings the profile is growing and growing, even when a user delets his mails in Thunderbird.
delete mails physicaly after the default threshold (performance)
i reported this bug also in Ubuntu, since that's the distri i use.
that bug has some information important to here:
this quote is from:
Basically tb version of bug 205756, also see bug 286888.
Confirming rather than duping to bug 205756 since that's morphed into the Seamonkey version.
Tagging "privacy" because we regularly hear from users horrified to find their "deleted" private mails are still sitting on their disk (often found after having them imported into another progam).
Tagging "dataloss" because of the max file-size and/or quota issues raised in comment 0.
Found an earlier version
*** This bug has been marked as a duplicate of bug 341206 ***