Le vendredi 30 octobre 2015, 13:28:52 Oswald Buddenhagen a écrit : > On Fri, Oct 30, 2015 at 12:18:58PM +0100, Mathieu ROY wrote: > > I hit the issue mentioned in > > http://sourceforge.net/p/isync/mailman/isync-devel/thread/20140617155518. > > GA5871@1ksurvivor/ [...] > > Selecting master INBOX... > > Selecting slave INBOX... > > Loading master... > > Loading slave... > > slave: 27 messages, 0 recent > > master: 16 messages, 0 recent > > Synchronizing... > > [...] > > > > As you can see, it notice the desync but does not act upon it. > > this is a dead giveaway that your diagnosis is incorrect - it wouldn't > select the mailbox if it was ignoring it. > your problem may be related to the uids having temporarily gone through > the roof for some reason; you can adjust the state file to reduce the > maximum seen uids to zero, thus forcing a complete resync of new > messages. there have been related threads on the list before.
Hello Oswald, It was not really clear to me how to "reduce the maximum seen uids to zero" (and a search on the archives was kind of tedious, even though it looks like the issue often relates to dovecot, which I'm using). I just renamed the relevant .mbsyncstate It duplicated the missing messages, I removed them afterwards. This is dirty heck but that'll do for me for now. Thanks for the help Regards, -- http://yeupou.wordpress.com/ ------------------------------------------------------------------------------ _______________________________________________ isync-devel mailing list isync-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/isync-devel
