Re: Isync 1.1.1 client->server update failure

[Oswald B. <osw...@gm...>]

On Fri, Jun 27, 2014 at 12:41:49PM +0400, Evgeniy Berdnikov wrote:
> --- /var/mail/berd/.uidvalidity ----------------------------------------
> 1245525174
> 400048
> ------------------------------------------------------------------------
> 
> --- /var/mail/berd/.mbsyncstate ----------------------------------------
> MasterUidValidity 1185439805
> SlaveUidValidity 1245525174
> MaxPulledUid 454606
> MaxPushedUid 401558
> 
got it:
for some reason, your MaxPushedUid is higher than the highest UID in
your mailbox (second line in .uidvalidity), so whatever new messages
appear in the mailbox, mbsync thinks it already dealt with them.
judging by the contents of the sync state, the UIDs in the mailbox
actually do reach that high, so for some unholy reason the highest UID
got rewound (and after adding a few more new messages you are going to
get complaints about duplicate UIDs). any idea how that happened?
anyway, you can fix it by setting the highest UID to 402000 for example.