[Dovecot] dsync problem: Error: Can't rename mailbox INBOX
Hi all,
I'm running two debian machines with dovecot 2.0.9 autobuilds and would like to keep mails synchronized on both via dsync. Mails are kept in maildir on both sides. While syncing, dsync gives the following error:
dsync-local(jan.binder): Error: Can't rename mailbox INBOX to INBOX_a432bf2eca595a4dba47000043b078f4: Renaming INBOX isn't supported. dsync-local(jan.binder): Error: Can't rename mailbox INBOX_e184273887675a4dcc5b00000c16d079 to INBOX: Target mailbox already exists
Further diagnostic information: dsync command: dsync -D -v -f mirror ssh jan.binder@firefly.local dsync
dovecot -n on firefly.local: # 2.0.9 (159605040ec0): /etc/dovecot/dovecot.conf # OS: Linux 2.6.37-trunk-686-bigmem i686 Debian wheezy/sid managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date passdb { driver = pam } plugin { sieve = ~/.dovecot.sieve sieve_dir = ~/sieve } protocols = imap lmtp ssl_cert =
dovecot -n on depth.local: # 2.0.9 (049a922c193c): /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-5-amd64 x86_64 Debian wheezy/sid managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date passdb { driver = pam } plugin { sieve = ~/.dovecot.sieve sieve_dir = ~/sieve } protocols = imap lmtp ssl_cert =
Should this usage of dsync work in principle?
Best regards, Jan Binder
On Thu, 2011-02-17 at 14:25 +0100, Jan Binder wrote:
dsync-local(jan.binder): Error: Can't rename mailbox INBOX to INBOX_a432bf2eca595a4dba47000043b078f4: Renaming INBOX isn't supported. dsync-local(jan.binder): Error: Can't rename mailbox INBOX_e184273887675a4dcc5b00000c16d079 to INBOX: Target mailbox already exists
Syncing INBOX is a bit weak point with dsync currently. Basically the problem is that the local and remote INBOX has a different mailbox GUID, so dsync treats them as different mailboxes that have a naming conflict. The usual way to resolve this by renaming doesn't work, because INBOX can't be renamed.
You should be able to solve this by deleting the INBOX manually from the other side and letting dsync create it again with the proper GUID. What mailbox format do you use? I don't see mail_location in your settings.
Am Donnerstag 17 Februar 2011, 17:14:45 schrieb Timo Sirainen:
On Thu, 2011-02-17 at 14:25 +0100, Jan Binder wrote:
dsync-local(jan.binder): Error: Can't rename mailbox INBOX to INBOX_a432bf2eca595a4dba47000043b078f4: Renaming INBOX isn't supported. dsync-local(jan.binder): Error: Can't rename mailbox INBOX_e184273887675a4dcc5b00000c16d079 to INBOX: Target mailbox already exists
Syncing INBOX is a bit weak point with dsync currently. Basically the problem is that the local and remote INBOX has a different mailbox GUID, so dsync treats them as different mailboxes that have a naming conflict. The usual way to resolve this by renaming doesn't work, because INBOX can't be renamed.
Thanks for your explanation, I will try deleting and syncing.
You should be able to solve this by deleting the INBOX manually from the other side and letting dsync create it again with the proper GUID. What mailbox format do you use? I don't see mail_location in your settings.
I'm using a maildir++ storage located in ~/Maildir . Dovecot seems to use this by default and without complaining. Is it a good idea to set mail_location ?
Am Donnerstag 17 Februar 2011, 17:14:45 schrieb Timo Sirainen:
On Thu, 2011-02-17 at 14:25 +0100, Jan Binder wrote:
dsync-local(jan.binder): Error: Can't rename mailbox INBOX to INBOX_a432bf2eca595a4dba47000043b078f4: Renaming INBOX isn't supported. dsync-local(jan.binder): Error: Can't rename mailbox INBOX_e184273887675a4dcc5b00000c16d079 to INBOX: Target mailbox already exists
Syncing INBOX is a bit weak point with dsync currently. Basically the problem is that the local and remote INBOX has a different mailbox GUID, so dsync treats them as different mailboxes that have a naming conflict. The usual way to resolve this by renaming doesn't work, because INBOX can't be renamed.
You should be able to solve this by deleting the INBOX manually from the other side and letting dsync create it again with the proper GUID. What mailbox format do you use? I don't see mail_location in your settings.
Ok. deleting INBOX doesn't make dsync work: dsync-local(jan.binder): Error: Can't rename mailbox INBOX to INBOX_a432bf2eca595a4dba47000043b078f4: Renaming INBOX isn't supported.
I deleted the INBOX folder on the machine where the dsync command is run from and after the failed sync it still does not exist.
Does my problem have anything to do with the maildir++ storage format specifically? There doesn't seem to be any documentation on what works and what doesn't work.
participants (2)
-
Jan Binder
-
Timo Sirainen