[Tickets #13852] Re: No Virtual Trash

[noreply at bugs.horde.org]

BITTE NICHT AUF DIESE NACHRICHT ANTWORTEN. NACHRICHTEN AN DIESE  
E-MAIL-ADRESSE WERDEN NICHT GELESEN.

Ticket-URL: https://bugs.horde.org/ticket/13852
------------------------------------------------------------------------------
  Ticket           | 13852
  Aktualisiert Von | Jan Schneider <jan at horde.org>
  Zusammenfassung  | No Virtual Trash
  Warteschlange    | IMP
  Version          | Git master
  Typ              | Bug
  Status           | Feedback
  Priorität        | 1. Low
  Milestone        |
  Patch            |
  Zuständige       | Michael Slusarz
------------------------------------------------------------------------------


Jan Schneider <jan at horde.org> (2015-02-25 08:27) hat geschrieben:

>> Now that's one of a hidden setting. I never use Virtual Trash, so
>> when has it been moved there?
>
> Between IMP 4 and IMP 5.

I found the old behavior with a checkbox to enable the virtual trash  
more intuitive. But I don't have a strong opinion about this either.

>> Now that I was able to enable Virtual Trash, it's broken though:
>> - You still see deleted messages in the regular mailboxes.
>
> Can't reproduce.
>
>> - You cannot undelete messages.
>
> Fixed.

Needs to be backported too. Thanks!

>> - You can drag messages from the VT to any folder while they stay deleted.
>
> The current behavior is correct.  If you "move" a message out of  
> Virtual Trash, it will disappear from virtual trash.  But since the  
> message has a deleted flag, it will "re-appear" when the virtual  
> trash is explicitly refreshed (i.e. the search is run again).  This  
> is consistent semantics with every other search mailbox.

It's not the same completely. Because if you move from a search  
mailbox to a folder so that it doesn't match the search criteria  
anymore, it works like a regular mailbox. And that's the more  
important point. If we use the folder semantics with search results,  
we need to use the folder semantics in user interaction too. Where we  
cannot guarantee this interaction behavior, we need to disable it. If  
we don't want to re-run the search immediately (which would be the  
correct behavior) because it is too performance hungry, we need to  
disable moving out of search folders. If we don't want to undelete  
message after moving from a virtual trash for whatever reasons (which  
would be the correct behavior too), we again need to disable moving.