Move/copy shared Subfolder

[bofh]

Hello,

Interresting Problem.

I Tried teh following:
Account A get the share from Account B.
Its a Mail folder.
I can read and write mail there (so from a i can also drop a collection mails and so on)
i also cann create a subfolder.

But i cannot move a hole Folder from or to the share.

Means if i try to move a subfolder from the share i get the Message i cannot move that folder to that Destination.
When i try move or copy a folder to the share i get an unknown error

method:    FolderActionRequest
msg:    cannot copy object: 36889
code:    mail.CANNOT_COPY
detail:    soap:Sender
trace:    com.zimbra.cs.mailbox.MailServiceException: cannot copy object: 36889 ExceptionId:btpool0-86://group.example.com/service/soap/FolderActionRequest:1280336898547:599f6e2154cfbba1 Code:mail.CANNOT_COPY Arg:(itemId, IID, "36889") at com.zimbra.cs.mailbox.MailServiceException.CANNOT_COPY(MailServiceException.java:359) at com.zimbra.cs.service.mail.ItemActionHelper.executeRemote(ItemActionHelper.java:610) at com.zimbra.cs.service.mail.ItemActionHelper.schedule(ItemActionHelper.java:316) at com.zimbra.cs.service.mail.ItemActionHelper.MOVE(ItemActionHelper.java:109) at com.zimbra.cs.service.mail.ItemAction.handleCommon(ItemAction.java:140) at com.zimbra.cs.service.mail.FolderAction.handle(FolderAction.java:108) at com.zimbra.soap.SoapEngine.dispatchRequest(SoapEngine.java:420) at com.zimbra.soap.DocumentHandler.proxyRequest(DocumentHandler.java:491) at com.zimbra.soap.DocumentHandler.proxyRequest(DocumentHandler.java:462) at com.zimbra.cs.service.mail.ItemAction.proxyRemoteItems(ItemAction.java:297) at com.zimbra.cs.service.mail.ItemAction.handleCommon(ItemAction.java:116) at com.zimbra.cs.service.mail.FolderAction.handle(FolderAction.java:108) at com.zimbra.soap.SoapEngine.dispatchRequest(SoapEngine.java:420) at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.java:274) at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.java:158) at com.zimbra.soap.SoapServlet.doWork(SoapServlet.java:291) at com.zimbra.soap.SoapServlet.doPost(SoapServlet.java:212) at javax.servlet.http.HttpServlet.service(HttpServlet.java:727) at com.zimbra.cs.servlet.ZimbraServlet.service(ZimbraServlet.java:181) at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1166) at com.zimbra.cs.servlet.SetHeaderFilter.doFilter(SetHeaderFilter.java:79) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157) at org.mortbay.servlet.UserAgentFilter.doFilter(UserAgentFilter.java:81) at org.mortbay.servlet.GzipFilter.doFilter(GzipFilter.java:132) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:388) at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216) at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182) at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:765) at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:418) at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230) at org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114) at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152) at org.mortbay.jetty.handler.rewrite.RewriteHandler.handle(RewriteHandler.java:230) at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152) at org.mortbay.jetty.handler.DebugHandler.handle(DebugHandler.java:77) at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152) at org.mortbay.jetty.Server.handle(Server.java:326) at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:543) at org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:939) at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:755) at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:218) at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:405) at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:409) at org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:451)
request:    

docs@example.com0_523d414ee343aea4de477bb1d5d151a9ef94330f_69643d33363a66313632343434302d633536622d343537632d616265662d6161666565353932323437383b6578703d31333a313238303333393838373133333b6169643d33363a64656139343331362d633961302d343665622d386630332d6563653332656238326231343b747970653d363a7a696d6272613b

but i can create new folder and delete (old and new folder) without an issue.

The share has admin permissions.
I Tried it with the webinterface (netwokr edition)
Zimbra desktop 2.0 beta
Outlook with connector

No luck in any direction - moving subfolders

so the only workaround i see at the moment is export the hole structure to a tar.gz and reimport in the target account.

any better ideas ? its really bad if i have to make a new Folder move mails and then delete the original subfolder. that cant be the way in zimbra i means this is a very basic

[bdial]

been like this since 5.x, but i can't seem to find a rfe for it. i can't believe one hasn't been filed, i'm just not good at searching bugzilla.

[bofh]

Damn,.. and i hoped so much i got a misconfig on my server - i prayed for a mistake by myself :-)

ok i found it: Bug 43733 – Can't move subfolders in shared email folder

just type subfolder in the searchbox got 2 similar bugs but this seems the relevant one

PLEASE VOTE

[bofh]

oh man are you kiddn

it looks like its really just a rule which prevent from moving folder - to prevent such an expensive operation and killing the server.

so far so bad.

but the real fun is.
you can import into an shared folder from outlook:

ife moved the folder to an secondary pst file
and used outlooks import direktly into the shared account
(the zimbra import lost 200 of 600mb somehow)

we will see if there are some issues with that but it looks good.


this is really anoying, specially i dont know how i can explain this behaivior to an customer - really ife no idea.