[Tickets #8468] Re: Renaming public folder is wrong

bugs at horde.org bugs at horde.org
Wed Aug 5 21:18:49 UTC 2009


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

Ticket URL: http://bugs.horde.org/ticket/8468
------------------------------------------------------------------------------
  Ticket             | 8468
  Updated By         | Michael Slusarz <slusarz at horde.org>
  Summary            | Renaming public folder is wrong
  Queue              | IMP
  Version            | 4.3.4
  Type               | Bug
  State              | Feedback
  Priority           | 2. Medium
  Milestone          | 4.3.5
  Patch              |
  Owners             | Michael Slusarz
------------------------------------------------------------------------------


Michael Slusarz <slusarz at horde.org> (2009-08-05 17:18) wrote:

> An approach might be (pseudo code):
>
> if ($newfolder starts with "non-empty namespace") {
>     // INBOX.test1 - should be ok to use $newfolder
> } else {
>     if ($newfolder doesn't contain delimiter  - '.' im my server) {
>         // test1
>         $newfolder = defaultnamespace . $newfolder;
>     } elseif ($newfolder "starts with existing foldername") {
>         // i.e. group.test.test1 ->
>         // group.test exists already -> use $newfolder
>         // if a user wants to create/rename to  
> INBOX.group.test.test1 (a rare case IMHO)
>         // he has to type INBOX.group.test.test1
>     } elseif () {
>         // other.folder
>         $newfolder defaultnamespace . $newfolder;
>     }
> }

What if the user wants to rename 'group.test.test1' to 'foo.test2'.   
It would fall through to your last case and get added as  
'INBOX.foo.test2' which is not correct.

There are only two ways I can think of to fix:
1. Look at the old mailbox name and only allow a rename within that namespace.
2. Requiring the entire folder name while renaming, but this was what  
was specifically refused in the previously mentioned ticket since  
personal namespaces should be invisible to the user.

This is why Cyrus' namespace setup has *never* made sense to me.  The  
default namespace should be a user's personal namespace - shared and  
other folders are special folders that should live under a specific  
sub-folder.






More information about the bugs mailing list