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

[bugs at horde.org]

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

Ticket URL: http://bugs.horde.org/ticket/8468
------------------------------------------------------------------------------
  Ticket             | 8468
  Updated By         | frank.richter at hrz.tu-chemnitz.de
  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
------------------------------------------------------------------------------


frank.richter at hrz.tu-chemnitz.de (2009-08-05 06:27) wrote:

> Take 2 - try this latest patch.  Essentially, it doesn't try to  
> auto-magically add namespace information.

The same behavior as with the previous patch:
Renaming group.* (namespace '') folder is ok, renaming in INBOX  
namespace is wrong.
I'd like to rename "test" (in INBOX) to "test1",
IMP aks for new name for "test" (not "INBOX.test"), I give "test1"
This leads to:  Rename INBOX.test test1  ->  Permission denied

It's a bit tricky for IMP to detect which namespace a folder should go  
to (if an "empty" namespace '' exists).
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;
     }
}

Frank