On Thu, Nov 14, 2024 at 12:44:50PM +1100, sourcefo...@plast.id.au wrote:
I assume this is the way that I can fix my problem? I can grep through all my `.mbsyncstate` files for `0` in the first field, then delete the corresponding messages. I'm not entirely sure what the `0` means; do you think it's a reliable marker that the message is a duplicate for me? I can run some tests anyway and check this.
the zero is the UID of the far-side message, i.e. none at all, i.e., the near-side message got orphaned. so it is reliable, provided you have no legitimate reason for having such pairs (that would be the case when using MaxMessages; can't think of another one right now). _______________________________________________ isync-devel mailing list isync-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/isync-devel
