local side is greater than far side

[<sou...@pl...>]

Hi,

I have three systems running mbsync. On some systems, the near side has *more* emails than the far side. I've been using mbsync for years, and this is the first time I've noticed this problem. Possibly related to 1.5.0?

On the broken system, you can see that there are 147 emails (near side), but only 121 on the server (far side).

```
$ mbsync -V --pull foo:INBOX
Reading configuration file /home/username/.mbsyncrc
Channel foo                                                
Opening far side store foo-remote...
Resolving mail.bar.id.au...
Opening near side store foo-local...
Connecting to mail.bar.id.au (<IP_redacted>)... 
Connection is now encrypted
Logging in...
Authenticating with SASL mechanism PLAIN...
Opening far side box INBOX...                                 
Opening near side box INBOX...
Loading far side box...
Loading near side box...
near side: 147 messages, 0 recent
far side: 121 messages, 0 recent
Synchronizing...
Processed 1 box(es) in 1 channel(s),
pulled 0 new message(s) and 0 flag update(s).
```

On the working system, you can see that the near side correctly has 121 emails.

```
$ mbsync -V --pull foo:INBOX
Reading configuration file /home/username/.mbsyncrc
Channel foo                                                
Opening far side store foo-remote...
Resolving mail.bar.id.au...
Opening near side store foo-local...
Connecting to mail.bar.id.au (<IP_redacted>)... 
Connection is now encrypted
Logging in...
Authenticating with SASL mechanism PLAIN...
Opening far side box INBOX...                                 
Opening near side box INBOX...
Loading far side box...
Loading near side box...
near side: 121 messages, 0 recent
far side: 121 messages, 0 recent
Synchronizing...
Processed 1 box(es) in 1 channel(s),
pulled 0 new message(s) and 0 flag update(s),
pushed 0 new message(s) and 0 flag update(s).
```

I tried editing `.mbsyncstate` and setting both `MaxPulledUid` and `MaxPushedUid` to zero on the broken system, but this did not fix the problem. Further, it doesn't seem to be system-specific, because a different mailbox is broken on the "working" system.

Thank you in advance.