On Sun, Nov 29, 2015 at 06:22:32PM +0100, Thomas Koch wrote: > On Thursday 12 November 2015 23:21:21 Oswald Buddenhagen wrote: > > mbsync 1.2 can propagate mailbox deletions if configured so, which > > should leave you without stale sync states when used correctly. > > What do you mean with "used correctly"? > sync after each structural change, and delete only the cur/new/tmp subdirectories of slave-side mailboxes if you use SyncState *.
> I suppose that the following scenario still would lead to errors: > > 1) folder exists on server and is synced to client > 2) delete folder on server > 3) create new folder with the same name > 4) run isync yes, it would. you need to sync between 2 and 3. > > other than that, you can just manually delete the state files. > > Manually SSH-ing into the server after each folder deletion doesn't > really sound like a solution to me. > why exactly would there be mbsync state files on the server? ------------------------------------------------------------------------------ Go from Idea to Many App Stores Faster with Intel(R) XDK Give your users amazing mobile app experiences with Intel(R) XDK. Use one codebase in this all-in-one HTML5 development environment. Design, debug & build mobile apps & 2D/3D high-impact games for multiple OSs. http://pubads.g.doubleclick.net/gampad/clk?id=254741551&iu=/4140 _______________________________________________ isync-devel mailing list isync-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/isync-devel