On Wed, Jul 10, 2024 at 11:34:59AM +0000, Thomas Bergheim wrote:
Everything works great, except for this bug.
isync just thinks it already synced everything it should have. the log merely reflects a static state, so it doesn't help with figuring out how this happened. you can work around the state by hacking MaxPulledUID in the mbsyncstate files; there are numerous related threads here.
And it happens often enough that I am wondering if there is any long term solution to this problem?
it might be fixed in master, but that is buggy in other ways. _______________________________________________ isync-devel mailing list isync-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/isync-devel
