* Oswald Buddenhagen <oswald.buddenha...@gmx.de> [2021-11-30 15:15]: > On Tue, Nov 30, 2021 at 01:45:27PM +0100, Peter P. wrote: > > * Oswald Buddenhagen <oswald.buddenha...@gmx.de> [2021-11-29 19:22]: > > > try hacking that box' .mbsyncstate: set MaxPushedUid to 0. > > > > Thanks Oswald, setting it to zero made the sync work! > > > ok. it would be interesting to know how you got into that state, as there > was clearly something not quite as expected. maybe keep an eye on it, and if > it happens again try to remember as many circumstances as you can. My other email message about two folders not holding the same number of messages might be related (see there). It is with the same server folder trying to sync it to another computer.
> > One thing puzzles me still, why did the following command sync the > > server contents despite me giving the --noop flag? > > > > mbsync -V --noop --push account:INBOX/Trash > > > because you specified --push ... > it's actually a nonsensical combination, and it would be preferable if it > errored out instead of "letting push win", but the command merging code > borders on black magic, and i don't feel masochistic enough to touch it > again. :'-D Ok, that makes it more clear. I thought there would be a flag that would tell me what would happen (like rsync's --dry-run) before actually running a "push" sync. Is there another way to predict what would happen here? much appreciated, P _______________________________________________ isync-devel mailing list isync-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/isync-devel
