Unfortunately, you won't be able to simply drop in a new zmmboxmove file. Support does have a script that can be used to assist in recovering from accounts that have been moved already, but you'll need to upgrade to avoid this. I wouldn't suggest just relying on the script to get you out of this and buy you time until you can upgrade, as it has not been tested with long-term use like that. It's known to work in all the cases we've seen so far though.
From: "Tim Ross" <tross@calpoly.edu>
To: "zimbra-hied-admins" <zimbra-hied-admins@sfu.ca>
Sent: Monday, August 19, 2013 7:04:56 PM
Subject: Re: Migrating accounts and HSM volumes
Ryan,
I think you are right. That bug sounds exactly like the problem. Unfortunately, I can't upgrade the old and new systems at this point, so maybe Zimbra will be able to give me an updated zmmboxmove file I can use.
Thanks,
From: "Ryan Tandy" <rtandy@sd63.bc.ca>
To: "Tim Ross" <tross@calpoly.edu>
Cc: "zimbra-hied-admins" <zimbra-hied-admins@sfu.ca>
Sent: Monday, August 19, 2013 3:46:47 PM
Subject: Re: Migrating accounts and HSM volumes
Hi Tim,
On 13-08-19 03:20 PM, Tim Ross wrote:
> Unfortunately, neither of these processes apparently reset the Volume ID
> associated with each mail item. So, we end up with some folders or
> messages that can't be accessed and give a "No Such Volume" error when
> clicked.
If I've understood you correctly and you're currently running 7.2.x,
that sounds like http://bugzilla.zimbra.com/show_bug.cgi?id=79581 which
luckily should be fixed in the next point release...
--
Ryan Tandy - Programmer/Analyst rtandy@sd63.bc.ca
School District 63 (Saanich) +1 250 652 7385