Bug 1678856 Comment 10 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

(In reply to Dan Pernokis from comment #7)
> ...
> But the wording needs to be bare-bones simple:  "Compacting of folders is required.  Compact now?  Y/N"  (or two buttons, "Compact Now" and "Later", instead of "Y/N").  That gets the point across without confusion, without excess explanations that Average User likely won't understand anyway, and in a manner that is straightforward and do-able.  Pop it up EVERY time once the threshold is reached and it will get done eventually.

Long explanations will not get approved.  So yes, Short is better. 

> (Or maybe we should just force the issue and compact automatically if the threshold is, say, doubled -- but that opens another can of worms...)

Bug 286888 is frankly be a no brainer. We should just do it.

> BTW, given that email is a common way to distribute photos (either by attachment or by embedding), and given that typical photos today are MBs rather than KBs, then perhaps the default threshold needs to be raised.  Doesn't take many moved or deleted photo messages to exceed the limit.  I think the main deterrent to compacting is that it happens too frequently these days and takes too long (too many messages kept long-term in INBOX).

Please file a new bug for this. You can model on the last increase which was done in Bug 1462666 - increase default autocompact threshold "mail.purge_threshhold"  (Maybe bump to 1gb?)

> I have spent so many hours of my time explaining what is going on when people get this pop up. If I was charging my time then it would be fast approaching a four figure number. There are many more instances in the Support Forum than mentioned and some of those questions have several people posting comments. This is not just a couple of people and not everyone gets loads of emails, so many people will not see this pop up in the first fews weeks. It will continue to cause confusion and concern.

You don't need to do that/you shouldn't do that - it's not a good use of your time.  Just improve the KB article and point users to it.
(In reply to Dan Pernokis from comment #7)
> ...
> But the wording needs to be bare-bones simple:  "Compacting of folders is required.  Compact now?  Y/N"  (or two buttons, "Compact Now" and "Later", instead of "Y/N").  That gets the point across without confusion, without excess explanations that Average User likely won't understand anyway, and in a manner that is straightforward and do-able.  Pop it up EVERY time once the threshold is reached and it will get done eventually.

Long explanations will not get approved.  So yes, Short is better. 

> (Or maybe we should just force the issue and compact automatically if the threshold is, say, doubled -- but that opens another can of worms...)

Bug 286888 is frankly a no brainer. We should just do it.

> BTW, given that email is a common way to distribute photos (either by attachment or by embedding), and given that typical photos today are MBs rather than KBs, then perhaps the default threshold needs to be raised.  Doesn't take many moved or deleted photo messages to exceed the limit.  I think the main deterrent to compacting is that it happens too frequently these days and takes too long (too many messages kept long-term in INBOX).

Please file a new bug for this. You can model on the last increase which was done in Bug 1462666 - increase default autocompact threshold "mail.purge_threshhold"  (Maybe bump to 1gb?)

> I have spent so many hours of my time explaining what is going on when people get this pop up. If I was charging my time then it would be fast approaching a four figure number. There are many more instances in the Support Forum than mentioned and some of those questions have several people posting comments. This is not just a couple of people and not everyone gets loads of emails, so many people will not see this pop up in the first fews weeks. It will continue to cause confusion and concern.

You don't need to do that/you shouldn't do that - it's not a good use of your time.  Just improve the KB article and point users to it.

Back to Bug 1678856 Comment 10