Re: Replication not working - GUIDs conflict - will be merged later

2022-08-28 Thread Patrick Westenberg
Here are some logs, maybe related to my problem. Aug 23 20:43:57 Panic: doveadm(m...@example.com)<1355655>: file dsync-brain-mailbox.c: line 883 (dsync_brain_slave_recv_mailbox): assertion failed: (memcmp(dsync_box->mailbox_guid, local_dsync_box.mailbox_guid, sizeof(dsync_box->mailbox_guid)) =

Re: Replication not working - GUIDs conflict - will be merged later

2022-08-03 Thread Christian Mack
Hello Am 02.08.22 um 20:24 schrieb Gerald Galster: > >> (we're using maildir, so I can just rsync the individual mails/folders) > > I'm curious if anybody experienced this issue using mdbox. > As far as I remember it's better suited for replication as filenames > and location do not change on di

Re: Replication not working - GUIDs conflict - will be merged later

2022-08-02 Thread Gerald Galster
> (we're using maildir, so I can just rsync the individual mails/folders) I'm curious if anybody experienced this issue using mdbox. As far as I remember it's better suited for replication as filenames and location do not change on disk (index only). Best regards Gerald

Re: Replication not working - GUIDs conflict - will be merged later

2022-08-02 Thread Paul Kudla (SCOM.CA Internet Services Inc.)
ok i went through this as well a bit there is a replication full sync variable (i am having trouble finding it) 24h is the default but i might have rebuilt dovecot modifying this default after i got things working i put everything back to default code. yep i did from dovecot-2.3.19/src/rep

Re: Replication not working - GUIDs conflict - will be merged later

2022-08-02 Thread Sebastian Marske
On 8/1/22 11:15, Patrick Westenberg wrote: > Very interesting new insights: > > When I use imapsync and let it synchronize mails from INBOX to > INBOX/testfolder, the automatic replication works fine. > All mails are synchronized between my two backends. > > > When I move the mails to the INB

Re: Replication not working - GUIDs conflict - will be merged later

2022-08-01 Thread Paul Kudla (SCOM.CA Internet Services Inc.)
OK thanks for the updates Long story short i went through a bunch of replication issues when i was first setting up dovecot. Most of which were fixed in 2.3.19 and i have not seen any issues since. in general i had to turn on the debugging mode (mail_debug = yes) and filter syslog by "repl

Re: Replication not working - GUIDs conflict - will be merged later

2022-08-01 Thread Patrick Westenberg
Very interesting new insights: When I use imapsync and let it synchronize mails from INBOX to INBOX/testfolder, the automatic replication works fine. All mails are synchronized between my two backends. When I move the mails to the INBOX (doveadm move -u m...@example.com INBOX mailbox INBOX/testf

Re: Replication not working - GUIDs conflict - will be merged later

2022-07-31 Thread Patrick Westenberg
Replication is fully setup between the two backend servers and worked like a charm for years. My manual replication was just a desperate trial. Am 31.07.22 um 14:47 schrieb Paul Kudla (SCOM.CA Internet Services Inc.): Ok This is speculation but i understand the issue at a programming leve

Re: Replication not working - GUIDs conflict - will be merged later

2022-07-31 Thread Paul Kudla (SCOM.CA Internet Services Inc.)
Ok This is speculation but i understand the issue at a programming level what needs to be understood is that imap's uids & ugid's are relative to the host server the email is coming from. this is generally not an issue with replication on cyrus or dovecot because the server and the replicat

Replication not working - GUIDs conflict - will be merged later

2022-07-31 Thread Patrick Westenberg
Hi everyone, I have a weird problem with replication that I'm unable to solve. A new account is sychronized from an external provider via imapsync. The mails end up on my backend1. I see that the folder structure is immediately replicated to backend2. However, a lot of mails are missing and "dov