dsync: INBOX Can't be deleted
Hi,
I am Migrating an old cyrus mailserver to dovecot.
in the old cyrus Mailserver all User Mailboxes are sub-mailboxes of their INBOX.
I have to preserve that structure.
During Migration with dsync I get these Errors:
Error: Mailbox INBOX sync: mailbox_delete failed: INBOX can't be deleted
Is there a way to work around these Errors ?
Thanks Christoph
Am 23.01.2016 um 10:30 schrieb Christoph Adomeit:
Hi,
I am Migrating an old cyrus mailserver to dovecot.
in the old cyrus Mailserver all User Mailboxes are sub-mailboxes of their INBOX.
I have to preserve that structure.
During Migration with dsync I get these Errors:
Error: Mailbox INBOX sync: mailbox_delete failed: INBOX can't be deleted
Is there a way to work around these Errors ?
Thanks Christoph
for multiple advanced imap settings at migration you might use imapsync not dsync
Best Regards MfG Robert Schetterer
-- [*] sys4 AG
http://sys4.de, +49 (89) 30 90 46 64 Franziskanerstraße 15, 81669 München
Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263 Vorstand: Patrick Ben Koetter, Marc Schiffbauer Aufsichtsratsvorsitzender: Florian Kirstein
On 23/01/16 15:33, Robert Schetterer wrote:
for multiple advanced imap settings at migration you might use imapsync not dsync Best Regards MfG Robert Schetterer Sure but imapsync does not preserve message UID's which means that users end up redownloading all their messages or message/UID mismatches will happen.
Sami
Am 23.01.2016 um 23:27 schrieb Sami Ketola:
On 23/01/16 15:33, Robert Schetterer wrote:
for multiple advanced imap settings at migration you might use imapsync not dsync Best Regards MfG Robert Schetterer Sure but imapsync does not preserve message UID's which means that users end up redownloading all their messages or message/UID mismatches will happen.
Sami
One Year ago i tested Migration with dsync and it never worked as awaited with non dovecot source server, hopefully somebody other may help you and dsync code is now good enough to fix your problem.
Best Regards MfG Robert Schetterer
-- [*] sys4 AG
http://sys4.de, +49 (89) 30 90 46 64 Franziskanerstraße 15, 81669 München
Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263 Vorstand: Patrick Ben Koetter, Marc Schiffbauer Aufsichtsratsvorsitzender: Florian Kirstein
On 24/01/16 11:38, Robert Schetterer wrote:
Am 23.01.2016 um 23:27 schrieb Sami Ketola:
On 23/01/16 15:33, Robert Schetterer wrote:
for multiple advanced imap settings at migration you might use imapsync not dsync Best Regards MfG Robert Schetterer Sure but imapsync does not preserve message UID's which means that users end up redownloading all their messages or message/UID mismatches will happen.
Sami
One Year ago i tested Migration with dsync and it never worked as awaited with non dovecot source server, hopefully somebody other may help you and dsync code is now good enough to fix your problem.
One year ago we made successfull migrations with dsync. What kind of problems you had with it? Since dsync is the way we basicly do all our migrations.
Sami
Am 24.01.2016 um 12:21 schrieb Sami Ketola:
On 24/01/16 11:38, Robert Schetterer wrote:
Am 23.01.2016 um 23:27 schrieb Sami Ketola:
On 23/01/16 15:33, Robert Schetterer wrote:
for multiple advanced imap settings at migration you might use imapsync not dsync Best Regards MfG Robert Schetterer Sure but imapsync does not preserve message UID's which means that users end up redownloading all their messages or message/UID mismatches will happen.
Sami
One Year ago i tested Migration with dsync and it never worked as awaited with non dovecot source server, hopefully somebody other may help you and dsync code is now good enough to fix your problem.
One year ago we made successfull migrations with dsync. What kind of problems you had with it? Since dsync is the way we basicly do all our migrations.
Sami
I didnt remember exactly , i think it was no preserve message UID's from courier source and additional namespace change on dovecot target however it was not a big problem with imapsync and advice the users to configure their clients to new server in total
Best Regards MfG Robert Schetterer
-- [*] sys4 AG
http://sys4.de, +49 (89) 30 90 46 64 Franziskanerstraße 15, 81669 München
Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263 Vorstand: Patrick Ben Koetter, Marc Schiffbauer Aufsichtsratsvorsitzender: Florian Kirstein
- Sami Ketola schrieb am 23.01.16 um 23:27 Uhr:
On 23/01/16 15:33, Robert Schetterer wrote:
for multiple advanced imap settings at migration you might use imapsync not dsync Best Regards MfG Robert Schetterer Sure but imapsync does not preserve message UID's which means that users end up redownloading all their messages or message/UID mismatches will happen.
IIRC that is not true. Some years ago I migrated a server to dovecot and managed to do it with proper UID migration. No clients were required to re-download Mail. Nor over IMAP neither POP3.
-Marc
-- [*] sys4 AG
http://sys4.de, +49 (89) 30 90 46 64 Franziskanerstraße 15, 81669 München
Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263 Vorstand: Patrick Ben Koetter, Marc Schiffbauer Aufsichtsratsvorsitzender: Florian Kirstein
On 26 Jan 2016, at 15:56, Marc Schiffbauer m@sys4.de wrote:
- Sami Ketola schrieb am 23.01.16 um 23:27 Uhr:
On 23/01/16 15:33, Robert Schetterer wrote:
for multiple advanced imap settings at migration you might use imapsync not dsync Best Regards MfG Robert Schetterer Sure but imapsync does not preserve message UID's which means that users end up redownloading all their messages or message/UID mismatches will happen.
IIRC that is not true. Some years ago I migrated a server to dovecot and managed to do it with proper UID migration. No clients were required to re-download Mail. Nor over IMAP neither POP3.
IMAP protocol doesn't have a way for clients to specify UIDs. Especially UIDVALIDITY can't be preserved in any way. IMAP clients don't necessarily make it clearly visible that they're redownloading mails though. With POP3 clients if they use the keep-mails-on-server it pretty much has to redownload mails as duplicates. Unless the UIDL was based on some email headers or such, the POP3 UIDL can't be preserved either.
- Timo Sirainen schrieb am 26.01.16 um 16:00 Uhr:
On 26 Jan 2016, at 15:56, Marc Schiffbauer m@sys4.de wrote:
- Sami Ketola schrieb am 23.01.16 um 23:27 Uhr:
On 23/01/16 15:33, Robert Schetterer wrote:
for multiple advanced imap settings at migration you might use imapsync not dsync Best Regards MfG Robert Schetterer Sure but imapsync does not preserve message UID's which means that users end up redownloading all their messages or message/UID mismatches will happen.
IIRC that is not true. Some years ago I migrated a server to dovecot and managed to do it with proper UID migration. No clients were required to re-download Mail. Nor over IMAP neither POP3.
IMAP protocol doesn't have a way for clients to specify UIDs. Especially UIDVALIDITY can't be preserved in any way. IMAP clients don't necessarily make it clearly visible that they're redownloading mails though. With POP3 clients if they use the keep-mails-on-server it pretty much has to redownload mails as duplicates. Unless the UIDL was based on some email headers or such, the POP3 UIDL can't be preserved either.
IDNRC ;-)
Then I am pretty sure that I used dsync. Because I AM sure that I had no issues with re-dpwnloadeing and that I had an eye on especially on that.
-Marc
-- [*] sys4 AG
http://sys4.de, +49 (89) 30 90 46 64 Franziskanerstraße 15, 81669 München
Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263 Vorstand: Patrick Ben Koetter, Marc Schiffbauer Aufsichtsratsvorsitzender: Florian Kirstein
Am 26.01.2016 um 16:29 schrieb Marc Schiffbauer:
- Timo Sirainen schrieb am 26.01.16 um 16:00 Uhr:
On 26 Jan 2016, at 15:56, Marc Schiffbauer m@sys4.de wrote:
- Sami Ketola schrieb am 23.01.16 um 23:27 Uhr:
On 23/01/16 15:33, Robert Schetterer wrote:
for multiple advanced imap settings at migration you might use imapsync not dsync Best Regards MfG Robert Schetterer Sure but imapsync does not preserve message UID's which means that users end up redownloading all their messages or message/UID mismatches will happen.
IIRC that is not true. Some years ago I migrated a server to dovecot and managed to do it with proper UID migration. No clients were required to re-download Mail. Nor over IMAP neither POP3.
IMAP protocol doesn't have a way for clients to specify UIDs. Especially UIDVALIDITY can't be preserved in any way. IMAP clients don't necessarily make it clearly visible that they're redownloading mails though. With POP3 clients if they use the keep-mails-on-server it pretty much has to redownload mails as duplicates. Unless the UIDL was based on some email headers or such, the POP3 UIDL can't be preserved either.
IDNRC ;-)
Then I am pretty sure that I used dsync. Because I AM sure that I had no issues with re-dpwnloadeing and that I had an eye on especially on that.
Hi Marc, you used dsync before on your project with success, then we tried it too on the "our" project, that failed ,so we used imapsync we ignored the problem with users pop3 letting their mails on the server or better ,we pre informed them what will happen.
-Marc
Best Regards MfG Robert Schetterer
-- [*] sys4 AG
http://sys4.de, +49 (89) 30 90 46 64 Franziskanerstraße 15, 81669 München
Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263 Vorstand: Patrick Ben Koetter, Marc Schiffbauer Aufsichtsratsvorsitzender: Florian Kirstein
On 23/01/16 11:30, Christoph Adomeit wrote:
Hi,
I am Migrating an old cyrus mailserver to dovecot.
in the old cyrus Mailserver all User Mailboxes are sub-mailboxes of their INBOX.
I have to preserve that structure.
During Migration with dsync I get these Errors:
Error: Mailbox INBOX sync: mailbox_delete failed: INBOX can't be deleted
Is there a way to work around these Errors ?
can you post doveconf -n and the command line you are invoking when executing dsync?
Sami
On 23 Jan 2016, at 11:30, Christoph Adomeit Christoph.Adomeit@gatworks.de wrote:
Hi,
I am Migrating an old cyrus mailserver to dovecot.
in the old cyrus Mailserver all User Mailboxes are sub-mailboxes of their INBOX.
I have to preserve that structure.
During Migration with dsync I get these Errors:
Error: Mailbox INBOX sync: mailbox_delete failed: INBOX can't be deleted
Is there a way to work around these Errors ?
With "doveadm backup" you have gotten into such a state that the INBOX needs to be deleted and recreated to preserve it exactly as it's in source. But you're using Maildir format, which doesn't allow deleting INBOX. So possibilities:
a) Don't use Maildir format
b) Delete the entire Maildir manually with rm -rf and the next doveadm backup should work (if not then something strange is going on)
participants (5)
-
Christoph Adomeit
-
Marc Schiffbauer
-
Robert Schetterer
-
Sami Ketola
-
Timo Sirainen