Well yes, the case you describe are working.
As a workaround we do :
A1 RENAME old1 new1
A2 RENAME new1 new1 our_partition
But this is bothering us as our software works as a cyrus replication protocol endpoint and we don't want to receive :
APPLY RENAME (old1 new1 partition default)
as default is not a usual partition that our software can handle.
On Mon, Mar 18, 2019 at 9:31 AM Michael Menge <michael.menge@xxxxxxxxxxxxxxxxxxxx> wrote:
Hi,
Quoting Sebastian Hagedorn <Hagedorn@xxxxxxxxxxxx>:
> Hi,
>
>> On cyrus 2.4.x we used to run
>> A1 RENAME mbox1 mbox2 our_partition
>>
>> When we run that on cyrus 3.0.8 we get :
>> A1 NO Cross-server or cross-partition move w/rename not supported
>>
>> Is there a way to do this rename with one command with cyrus3.
>> If we run A1 RENAME mbox1 mbox2
>> the mailbox is renamed as expected but it moves from our_partition to
>> default which is not what we want.
>>
>> Any suggestion ?
>
> I have no idea, because we're not far enough along in our migration
> to Cyrus 3, but this is troubling me. We currently use RENAME
> specifically for moving users cross-partition. If that isn't
> supported anymore, is there a new alternative in Cyrus 3?
I have not tested this, but I think you can move cross-partition
without rename
and rename without move cross-partition.
A1 RENAME mbox1 mbox1 our_partition
A2 RENAME mbox1 mbox2
Michael Menge
--------------------------------------------------------------------------------
M.Menge Tel.: (49) 7071/29-70316
Universität Tübingen Fax.: (49) 7071/29-5912
Zentrum für Datenverarbeitung mail:
michael.menge@xxxxxxxxxxxxxxxxxxxx
Wächterstraße 76
72074 Tübingen
----
Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
To Unsubscribe:
https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus
---- Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/ To Unsubscribe: https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus
