similar to: Duplicate mailbox id, mailbox does not exist when attempting to give a new guid

Hi all, When we run the below one user constantly shows as failed (dovecot version is 2.2.13): sudo doveadm replicator status "*" mail.log shows the below for the user: Jan? 3 16:20:57 hostname dovecot: dsync-server(user): Error: Duplicate mailbox GUID <guid number> for mailboxes <mailbox name.sub folder> and <mailbox name.sub folder> - giving a new GUID <guid

Hello, Am Montag, 15. Januar 2018, 13:54:22 CET schrieb Daniel Botting: > Hi all, > > When we run the below one user constantly shows as failed (dovecot > version is 2.2.13): > > sudo doveadm replicator status "*" > > mail.log shows the below for the user: > > Jan 3 16:20:57 hostname dovecot: dsync-server(user): Error: Duplicate > mailbox GUID

While migrating from mbox to maildir using dsync, I kept running into a brick wall. Some folders would not sync. The message in stderr was: Error message GUID: Mailbox GUIDs are not permanent without index files. This is what solved things for me. I hope this might help someone. Let me know if I'm completely off sides. When working with dsync to migrate from mbox to maildir format mailboxes,

I am migrating an old dovecot 2.2.30 (macOS High SIerra, macO S Server) to a new server with dovecot 2.3.7 (macOS Mojave, macports). To get the data over, I?m trying to do a reverse backup with doveadm between an old and a new mail server, but failing to do so. I?m trying (from the new server, the old server is 192.168.2.67): doveadm -Dv \ -o imapc_host=192.168.2.67 \ -o imapc_user=gerben \

Dovecot 2.1.7 While migrating mail from one server (Maildir) to another (mdbox), a config issue caused my dsync to fail on a few accounts. Those accounts received mail on the new server over night and it autocreated new inboxes with new GUIDs. Now dsync wants nothing to do with mirroring between the two (diff GUIDs). Is there a way to fix this? dsync(jeff at foo.bar): Error: Mailbox INBOX

Greetings all, I can view a mailbox's GUID like so: doveadm mailbox status -u guid However, how may I *modify* a mailbox GUID? Can this be done using doveadm or some other tool? If not, how may I go about modifying the dovecot.mailbox.log (where I assume GUID data is stored)? My specific use case has to do with me wanting to modify an existing mailbox's GUID so that its messages

On 10 Oct 2017, at 3.36, Jason Kiniry <jason.kiniry at gmail.com> wrote: > > Hi all, > > I've run into an issue with in-place mailbox format conversions between > mdbox and maildir and wondered if someone could assist. When using dsync to > convert a mailbox, the conversion loses a mailbox GUID and produces a > warning. This behavior seems to have been introduced

I have recently updated with 2.2.29.1-avh1~xenial1 ubuntu package on 16.04. It appears that I have a couple of duplicate GUIDs which fsck can't clear so the machine is looping through doing continuous fsck runs. Any way to determine what the offending messages are and how to delete or otherwise stop this? Jul 1 17:09:24 post dovecot: doveadm(djk at tobit.co.uk): Warning: fscking index

Hello, I am running dovecot 2.2.12 Current mail storage is sdbox and I am trying to compress all emails, which works fine, except for a few old mailboxes. If I run the following dsync command "dsync -u flea -o "mail_plugins=zlib" mirror maildir:~/ndbox" It fails with: dsync(flea): Error: Exporting mailbox INBOX failed: Backend doesn't support GUIDs, sync with header

Hi All! I'm also hitted by this problem. I'm trying to migrate emails from very old dbmail to dovecot (maildir). I read old threads with similar problem but I found only such solutions: - upgrade to 2.2.13 - workarround : use imapsync - no solution I'd like to not use imapsync, have you got an idea what should I do to do migration successfully? dsync throws: doveadm(root): Debug:

Hi, Here is a crash that's happening using the latest Dovecot version (v2.2.27 on CentOS7 x86_64): We are using replication. Judging by the second server's logs, I believe this has something to do with the fact that we're using the lazy_expunge plugin. Every night after midnight, we purge the lazy_expunge namespace by running a command similar to following one on the main server

Hi, I'm trying to migrate from Cyrus (remote side) to Dovecot 2.2.24 (local). On the local side the destinations folders, and indexes are empty. The command I'm using is doveadm \ -o mail_plugins= \ -o imapc_master_user=<cyrus-user> \ -o imapc_password=<cyrus-password> \ -o imapc_host=<cyrus-ip> \ \ -o imapc_ssl_verify=no

Hi all, I've run into an issue with in-place mailbox format conversions between mdbox and maildir and wondered if someone could assist. When using dsync to convert a mailbox, the conversion loses a mailbox GUID and produces a warning. This behavior seems to have been introduced between version 2.2.31 and 2.2.32. See below for the full debug output from both versions followed by the dovecot

Hi, I tried to import messages like this: doveadm import -u username at example.org mdbox:/mail/dovecot/example.org/username/mail mbox:/root/mail.txt all This seemed to have imported the same messages in the mail storage, as they were already there. And now I have got a lot of duplicates. Then I deleted the mbox:/root/mail mail stuff from "mailboxes" folder and the storage remained,

> On 9 Sep 2018, at 18.42, Andreas Thienemann <andreas at bawue.net> wrote: > > Hi, > > I am attempting to migrate a mailspool from a cyrus server to a dovecot server using the dsync backup approach as described in the wiki at <https://wiki.dovecot.org/Migration/Dsync>. > > The first attempt works great. Everything copies over and a quick glance over the spool

Hello, I'm aware of these two threads http://www.dovecot.org/pipermail/dovecot/2012-March/thread.html#134311 http://dovecot.org/pipermail/dovecot/2012-June/thread.html#136488 but unfortunately I wasn't successful with my dsync mailbox migration attempt despite the information I could find there. I'm using iRedMail setup for the dovecot server. I made sure that the dovecot mailbox

Hey, why i am getting this error ? dsync(user at example.com): Error: Can't rename mailbox VoIP_08300a224c41694c0d0f000020ce4ec5 to VoIP: Target mailbox already exists It happens when i run dsync twice, but it should do only changes right ? dovecot 2.0 I am traying to convert all my user mboc to maildir so i made an script to help. The enveriment: Have dovecot looking into file conf and

FWIW I just tried the sdbox mailbox format for a singe user (not the whole installation) by overriding the mail-userattr via ldap and the problem persists, so I don?t think it?s an issue with maildir per se, but rather a pop3 / replication issue or a misconfiguration on my side. Wolfgang > On 20 Jun 2015, at 22:29, Wolfgang Hennerbichler <wogri at wogri.com> wrote: > > Hi, >

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:

Hi Sami, On Sun, 9 Sep 2018, Sami Ketola wrote: > Is it possible to get imapc rawlogs to analyze? create a directory that is > writeable and add -o imapc_rawlog_dir=/path/to/directory to command line. Tried that. Thanks for the suggestion, that is actually really helpful. If anyone wants to play along at home, the files in that directory are created with the permissions of