On Mon, Jul 29, 2019 at 11:31:39PM +0530, Pankaj Jangid wrote: > If 'mbsync' drops the less interesting change then shouldn't the > problem get resolve automatically. This notice should not appear the > next time I run 'mbsync'. > yes, it should. but i seem to remember that someone pointed out that it doesn't happen in certain scenarios. are you running a full sync? what's your config+command line?
> pair (124660,81) > Notice: conflicting changes in (124660,81) > not pushing delete > > In these messages, what is interpretation of 'not pulling delete', 'not > pushing delete' and in my case the notice comes just above 'not pushing > delete'. > > As far as I have understood, it means, I have deleted the message locally > but I have done something else using some other client. So 'mbsync' is > not pushing my local delete to the server. Now do I need to scrap > through the mailbox files to find which is that message 124660,81? Or is > there an option/switch available to dig further using 'mbsync' command? > i suppose you need to add -Dd to make sense of the "pair" messages (the "entry" ones you skipped higher up, and the ones you didn't get from the drivers are supposed to provide enough context). but i don't remember the details - i wrote this stuff 15 years ago, with mostly just refactoring later on. and there is a good chance that the logging doesn't provide 100% case coverage. _______________________________________________ isync-devel mailing list isync-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/isync-devel
