x RENAME
should work
On 10/29/19 5:04 AM, David Phan wrote:
Hi,
Any update on this topic?
Regards,
David Phan
06.73.38.77.00
BlueMind
+33 (0)5 81 91 55 60
Hotel des Télécoms, 40 rue du village d'entreprises
31670 Labège, France
www.bluemind.net / https://blog.bluemind.net/fr/
---
Hi,
Any update on this topic?
Regards,
David Phan
06.73.38.77.00
BlueMind
+33 (0)5 81 91 55 60
Hotel des Télécoms, 40 rue du village d'entreprises
31670 Labège, France
www.bluemind.net / https://blog.bluemind.net/fr/
Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http:/
> Hi,
>
> seems that there is a problem with your cyrus quota tree
> (/var/lib/cyrus/quota) or at least some of its files.
In the case of RHEL6 this will be /var/lib/imap/quota/.
I suggest to look at the quota files there, they have names like
user. and are text files with two lines. Should be ea
Sorry, bad thread...
On 3/18/19 4:49 PM, Anthony Prades via Info-cyrus wrote:
> Hi,
>
> seems that there is a problem with your cyrus quota tree
> (/var/lib/cyrus/quota) or at least some of its files.
>
> Maybe strace command may help you find which files are corrupt:
> su - cyrus -c "strace /usr/
Hi,
seems that there is a problem with your cyrus quota tree
(/var/lib/cyrus/quota) or at least some of its files.
Maybe strace command may help you find which files are corrupt:
su - cyrus -c "strace /usr/lib/cyrus-imapd/quota user"
Anthony Prades
On 3/18/19 10:13 AM, Marco wrote:
> Il 18/03/
I will take look as to how/why this restriction was put into place. At
the very least, renaming a top-level mailbox and keeping it on the same
partition should be allowed.
On 3/18/19 4:57 AM, Thomas Cataldo wrote:
Well yes, the case you describe are working.
As a workaround we do :
A1 RENAM
Il 18/03/2019 08:25, Thomas Cataldo ha scritto:
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
Hi,
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
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 i
Hi,
Quoting Sebastian Hagedorn :
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 RENAM
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
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 a
12 matches
Mail list logo
