On Mon, Jul 29, 2019 at 04:46:48PM +0200, Oswald Buddenhagen wrote: > this is not really an issue. it's just telling you that you modified the > message in both stores in ways that cannot be reconciled (which means it > drops the less interesting change, e.g., a flag update on one end when > the message was deleted on the other end).
My use of wrong term here. Agree. This isn't an issue. Actually I
guessed it that there is conflict because of message being differently
updated by two clients.
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'.
> use the -D switch (or -Ds in particular for the above) as the man page
> says.
Thanks for this. I wasn't aware of '-s' option. I was debugging using
only '-Dmn'. Now I am probably closer to the solution. Here is the
output. Just that I am not aware how to interpret these message. I am
pasting here part of the output.
pair (124645,70)
not pulling delete
pair (124646,71)
not pushing delete
pair (124647,72)
pair (124650,75)
pair (124651,76)
pair (124652,77)
pair (124653,78)
not pulling delete
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?
Thanks.
--
Pankaj
Planet Earth.
""
A good scapegoat is hard to find.
A guilty conscience is the mother of invention.
-- Carolyn Wells
signature.asc
Description: PGP signature
_______________________________________________ isync-devel mailing list isync-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/isync-devel
