[Tickets #3788] NEW: "Empty Trash" button deletes all e-mail from INBOX with specific preferences defined

bugs@bugs.horde.org bugs at bugs.horde.org
Tue Apr 18 14:38:49 PDT 2006


DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/?id=3788
-----------------------------------------------------------------------
 Ticket             | 3788
 Created By         | poehler at nexcess.net
 Summary            | "Empty Trash" button deletes all e-mail from INBOX with specific preferences defined
 Queue              | IMP
 Version            | 4.1.1
 State              | Unconfirmed
 Priority           | 3. High
 Type               | Bug
 Owners             | 
-----------------------------------------------------------------------


poehler at nexcess.net (2006-04-18 14:38) wrote:

We upgraded very recently to the latest versions of Horde and IMP (3.3.1 &
4.4.1).

A client of ours managed to find a series of events that lead to all the 
mail from her INBOX being deleted when she clicked the "Empty Trash" menu
item.

I've managed to reproduce this.  Here's what I did.

Under:
Options for Mail -> Deleting and Moving Messages

CHECKED: When deleting messages, move them to your Trash folder instead of 
marking them as deleted?
UNCHECKED: Use Virtual Trash Folder?
Trash folder: [None]
CHECKED:  Display the "Empty Trash" link in the menubar?

With those options set, if you click the "Empty Trash" link in the menubar,

it will act as if the INBOX is the trash folder, and delete all the messages

in the INBOX.  The confirmation popup says "Are you sure you wish to empty
your trash folder?"

I understand why this occured, I think - having no trash folder specified 
made IMP treat the INBOX as the trash folder while emptying.  I don't think

this is intended behavior though.  The end user certainly wasn't expecting 
the mail in their INBOX to be deleted.  It seems to me that the "Empty 
Trash" link in the menubar should not appear if the selected trash folder is
[None].  That would prevent this from happening in the future.





More information about the bugs mailing list