Re: no full syncs after upgrading to dovecot 2.3.18

Ok update from my end under 2.3.18 (have not upgraded production to 2.3.19 yet) replication issues as stated before however i need to note that i had to manually sync a user that was not being listed as a replicator fail this means i have to force a full sync between servers on all account

Re: no full syncs after upgrading to dovecot 2.3.18

Hi Aki, We just installed 2.3.19, and are seeing a couple of users throwing the "INBOX/dovecot.index reset, view is now inconsistent" and their replicator status erroring out. Tried force-resync on the full mailbox, but to no avail just yet. Not sure if this bug was supposedly fixed in 2.3.19? T

Re: no full syncs after upgrading to dovecot 2.3.18

Thanks for the update I dont push anyone when asking for updates I am a programmer by trade as well and nothing ever goes as planned prefer we all take our time and roll it out correctly then jumping the gun. Why I am trying to help elsewhere as I have gotten pretty fluid with dovecot etc a

Re: no full syncs after upgrading to dovecot 2.3.18

2.3.19 is round the corner, so not long. I cannot yet promise an exact date but hopefully within week or two. Aki > On 28/04/2022 13:57 Paul Kudla (SCOM.CA Internet Services Inc.) > wrote: > > > Thanks for the update. > > is this for both replication issues (folders +300 etc) > > Just Ask

Re: no full syncs after upgrading to dovecot 2.3.18

Thanks for the update. is this for both replication issues (folders +300 etc) Just Asking - Any ETA Happy Thursday !!! Thanks - paul Paul Kudla Scom.ca Internet Services 004-1009 Byron Street South Whitby, Ontario - Canada L1N 4S3 Toronto 416.642.7266 Main 1.866.4

Re: Better not post your email password on a public mailing list, was: Re: no full syncs after upgrading to dovecot 2.3.18

thanks i love to share but sometime forget whats noted inside a config file Been meaning to change this for a while anyways. Happy Thursday !!! Thanks - paul Paul Kudla Scom.ca Internet Services 004-1009 Byron Street South Whitby, Ontario - Canada L1N 4S3 Toronto 4

Re: no full syncs after upgrading to dovecot 2.3.18

Hi! This is probably going to get fixed in 2.3.19, this looks like an issue we are already fixing. Aki > On 26/04/2022 16:38 Paul Kudla (SCOM.CA Internet Services Inc.) > wrote: > > > Agreed there seems to be no way of posting these kinds of issues to see > if they are even being addresse

Better not post your email password on a public mailing list, was: Re: no full syncs after upgrading to dovecot 2.3.18

Am 26.04.22 um 11:36 schrieb Paul Kudla (SCOM.CA Internet Services Inc.): #imapc_host = mail.scom.ca #imapc_password = Pk554669 #imapc_user = p...@scom.ca I suggest to change that password immediately. $ openssl s_client -crlf -connect mail.scom.ca:993 CONNECTED(0003) * OK [CAPABILITY IMAP

Re: no full syncs after upgrading to dovecot 2.3.18

Agreed there seems to be no way of posting these kinds of issues to see if they are even being addressed or even known about moving forward on new updates i read somewhere there is a new branch soming out but nothing as of yet? 2.4 maybe 5.0 my previous replication issues (ba

Re: no full syncs after upgrading to dovecot 2.3.18

ok until someone fixes the folder count (or i figure that out) the errors will stay on the replicator side and i use that error (knowing they are not replicating) coming back to trigger a background dsync with a python script through doveadm (seems to work) but this is a hack. [05:41:37] m

Re: no full syncs after upgrading to dovecot 2.3.18

more specific to this issue i looks like (at this was fun for me to figure out as well) note replication does not work well on nfs file systems etc i started with sdram drives on one server and nfs on the other and found i simply had to go sdram (or whatever) on the other one smoothed all

Re: no full syncs after upgrading to dovecot 2.3.18

side issue if you are getting inconsistant dsyncs there is no real way to fix this in the long run. i know its a pain (already had to my self) i needed to do a full sync, take one server offline, delete the user dir (with dovecot offline) and then rsync (or somehow duplicate the main serv

Re: no full syncs after upgrading to dovecot 2.3.18

Ah, I'm now getting errors in the logs, that would explains the increasing number of failed sync requests: dovecot: imap(x)<2961235>: Error: Mailbox INBOX: /vmail/l/i/x/dovecot.index reset, view is now inconsistent And sure enough: # dovecot replicator status x x n

Re: no full syncs after upgrading to dovecot 2.3.18

Hello, On my side we are running Linux (Debian Buster). I'm not sure my problem is actually the same as Paul or you Sebastian since I have a lot of boxes but those are actually small (quota of 110MB) so I doubt any of them have more than a dozen imap folders. The main symptom is that I have

Re: no full syncs after upgrading to dovecot 2.3.18

Hi there, thanks for your insights and for diving deeper into this Paul! For me, the users ending up in 'Waiting for dsync to finish' all have more than 256 Imap folders as well (ranging from 288 up to >5500; as per 'doveadm mailbox list -u | wc -l'). For more details on my setup please see my p

Re: no full syncs after upgrading to dovecot 2.3.18

Question having similiar replication issues pls read everything below and advise the folder counts on the non-replicated users? i find the total number of folders / account seems to be a factor and NOT the size of the mail box ie i have customers with 40G of emails no problem over 40 or