Last Comment Bug 177074 - should compact Inbox automatically if it is empty.
: should compact Inbox automatically if it is empty.
Status: NEW
Product: MailNews Core
Classification: Components
Component: Backend (show other bugs)
: Trunk
: x86 Linux
: -- enhancement with 1 vote (vote)
: ---
Assigned To: Nobody; OK to take it and work on it
Depends on: 61960
  Show dependency treegraph
Reported: 2002-10-28 00:26 PST by Edward Liu
Modified: 2012-08-07 05:09 PDT (History)
6 users (show)
See Also:
Crash Signature:
QA Whiteboard:
Iteration: ---
Points: ---


Description Edward Liu 2002-10-28 00:26:06 PST
User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2b) Gecko/20021016
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2b) Gecko/20021016

It is reasonable to zero the filesize of Inbox if Inbox is empty.
Mail check utilities rely on this to flag mail folder status.

Reproducible: Always

Steps to Reproduce:
1. Receive some mails
2. Delete all of them.
3. Check the 'Inbox' file in mozilla Mail directory.  It is not empty.

Actual Results:  
The file size of Inbox is not zero.

Expected Results:  
The file size of Inbox should be zero.
Comment 1 David :Bienvenu 2002-10-28 07:50:28 PST
one caveat - if we ever undo shift delete of local messages, we would not want
to compact empty folders immediately, because that would prevent us from undoing
that shift delete.
Comment 2 (not reading, please use instead) 2003-05-08 11:04:50 PDT
mass re-assign.
Comment 3 Hans Schleichert 2004-06-09 23:39:46 PDT
I agree on the suggestion to zero the inbox filesize, at least when the inbox
folder is emptied by the spam filter.
Comment 4 Jo Hermans 2006-02-01 04:09:49 PST
related to bug 61960
Comment 5 Wayne Mery (:wsmwk, NI for questions) 2006-04-24 08:50:58 PDT
Is this about local inbox?
Comment 6 (not reading, please use instead) 2007-06-21 15:03:23 PDT
sorry for the spam.  making bugzilla reflect reality as I'm not working on these bugs.  filter on FOOBARCHEESE to remove these in bulk.
Comment 7 Serge Gautherie (:sgautherie) 2008-06-20 10:44:51 PDT
Filter on "Nobody_NScomTLD_20080620"
Comment 8 Andrew 2012-08-06 12:41:49 PDT
This report is essentially a duplicate of another:

Both suggest to compact automatically.
Both - not required.
Both already implemented: there's a preference to allow automatic compaction. It works not only on Inbox, but on all folders.

A suggestion to compact after an action by spam filter is not good too.
Because the filter occasionally removes good messages. It is not a big difference whether you remove something by hand, or by filter. Both are accidents. Both need to be guarded against.

You suggest to help the accident propagate, and evolve.
Comment 9 Wayne Mery (:wsmwk, NI for questions) 2012-08-06 13:06:59 PDT
I think this bug, strictly speaking, is a subset of bug 286888.  But maybe Bienvenu or others think otherwise.

As for bug 286888, is not yet implemented. Yes, automatic compact is now the default. But that doesn't go far enough. The idea behind bug 286888 is to increase the level of "smartness" of automating compact, that absolutely no UI is needed, including preferences. 

So for example, it should be adaptive so that it is performant for widely varying folder sizes and message sizes.  Currently it does not do that.
Comment 10 Andrew 2012-08-07 04:17:06 PDT
My point is different: automating compact takes  away control from the user.
One may not want to compact at all for many reasons. Some are mentioned in the duplicate bug.

The default should be not to compact automatically.
Nothing should be lost without knowledge of user.

The point about "smartness" is pointless.
A compact is still a compact regardless of folder size, or apparent emptyness.

I do not see any essential difference between a non compacted folder with 1 message, and the same with no messages.
A person may still not want to compact.

If you think it is a duplicate, then close it. No need to keep many open bugs.
Comment 11 Wayne Mery (:wsmwk, NI for questions) 2012-08-07 05:09:31 PDT
it is not a duplicate

Note You need to log in before you can comment on or make changes to this bug.