Re: 2.3 replication issue throwing errors

Paul Kudla via dovecot <[email protected]>
Newsgroups gmane.mail.imap.dovecot
Message-ID <[email protected]>
I just wanted to provide an update as the replication issues are now 
resolved

i thanks you again for showing howto translate a GUID into a folder name 
however that did not provide enough info to cause a resync

it turns out all you have to do is manually delete the offending folder 
on the replica server and dovecot will resync immeditely

standard case of over thinking the issue.

hopes this helps someone else down the road when dsync throws reversal 
errors.



Thanks - Paul Kudla (Manager SCOM.CA Internet Services Inc.)

Have A Happy Sunday AND Happy Sucessful 2026 !

Scom.ca Internet Services <http://www.scom.ca>
104-1009 Byron Street South
Whitby, Ontario - Canada
L1N 4S3

Toronto 416.642.7266
Main 1.866.411.7266
Fax 1.888.892.7266
Email [email protected]

On 2026-02-20 8:43 a.m., Doug via dovecot wrote:
> 
>> -----Original Message-----
>> From: Paul Kudla via dovecot <[email protected]>
>> Sent: Friday, February 20, 2026 6:48 AM
>> To: Dovecot Mailing List <[email protected]>
>> Subject: 2.3 replication issue throwing errors
>>
>>
>> shows same error on both servers
>>
>> Server 1 :
>>
>> # sync [email protected]
>> doveadm([email protected])<90952><BJq9J2dHmGlIYwEA0dxyZQ>: Warning:
>> Mailbox
>> changes caused a desync. You may want to run dsync again: Remote lost
>> mailbox GUID f982a82747469869ea0f0100cf58dcff (maybe it was just
>> deleted?)
>>
>> Server 2:
>>
>> # sync [email protected]
>> doveadm([email protected])<90952><BJq9J2dHmGlIYwEA0dxyZQ>: Warning:
>> Mailbox
>> changes caused a desync. You may want to run dsync again: Remote lost
>> mailbox GUID f982a82747469869ea0f0100cf58dcff (maybe it was just
>> deleted?)
>>
>>
>> i am aware there is a mismatch on one of the servers but there does not
>> seem to be a clear cut way to find the offending file to delete it or
>> force a backwards sync ?
>>
>> How would i identify what GUID f982a82747469869ea0f0100cf58dcff
>> means?
>>
>> same on both servers.
>>
>> doveadm force-resync -u [email protected] '*'
>>
>> have tried reindex etc etc etc issue persists
>>
>> logs ??
>>
>> mail18       02-20 06:45:24 {dovecot}        [67632] (3014654310)
>> doveadm([email protected])<71073><hOl0ClRJmGmhFQEAz1jc/w>: Debug:
>> open(/proc/self/stat) failed: No such file or directory
>> mail18       02-20 06:45:24 {dovecot}        [67632] (3014654311)
>> doveadm([email protected])<71073><hOl0ClRJmGmhFQEAz1jc/w>: Debug:
>> open(/proc/self/io) failed: No such file or directory
>> mail18       02-20 06:45:24 {dovecot}        [67632] (3014654312)
>> doveadm([email protected])<71073><hOl0ClRJmGmhFQEAz1jc/w>: Debug:
>> Namespace
>> inbox: type=private, prefix=, sep=/, inbox=yes,
>>
>> hidden=no, list=yes, subscriptions=yes location=maildir:~/
>>
>>
>> any help would be appreciated
>>
>> --
>>
>>
>> Thanks - Paul Kudla (Manager SCOM.CA Internet Services Inc.)
>>
>> Have A Happy Friday AND Happy Sucessful 2026 !
>>
>> Scom.ca Internet Services <http://www.scom.ca>
>> 104-1009 Byron Street South
>> Whitby, Ontario - Canada
>> L1N 4S3
>>
>> Toronto 416.642.7266
>> Main 1.866.411.7266
>> Fax 1.888.892.7266
>> Email [email protected]
>>
> 
> This command should at least tell you which mail folder exhibits the issue
> 
> # doveadm mailbox status -u "[email protected]" guid "*" | grep f982a82747469869ea0f0100cf58dcff
> 
> Once you know the mailbox folder/name, look at the stats and drill down from there. Let's say the folder name is 'Saved Notifications'
> 
> # doveadm mailbox status -u "[email protected]" all "Saved Notifications"
> 
> -- Doug
> 
> _______________________________________________
> dovecot mailing list -- [email protected]
> To unsubscribe send an email to [email protected]
> 

_______________________________________________
dovecot mailing list -- [email protected]
To unsubscribe send an email to [email protected]
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.