On Thu, Jan 08, 2015 at 01:09:59PM +0100, Titus von der Malsburg wrote: > What is the problem here and how can I fix it? > so, with some additional information i now know more or less what is happening:
MaxPushedUid in .mbsyncstate is way above the highest UID ever known to the mailbox (as per .uidvalidity), so mbsync thinks it already synced messages that haven't even appeared yet (and won't for weeks or months to come according to my estimate). to get it running again it should be sufficient to reset MaxPushedUid to 0. the interesting question is how that came to be. looking at the numbers, it might well be a single flipped bit on disk, or an editor gone wild. who knows. somewhat worryingly, this is the second such case on this list. ------------------------------------------------------------------------------ Dive into the World of Parallel Programming! The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net _______________________________________________ isync-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/isync-devel
