Jeff Templon <templon@nikhef.nl> writes: > quote: "mbsync maintains a mapping of remote (col 1) to local (col 2) uids. > when you migrate, you can just duplicate the columns." > > He's talking about migrating a mail store from offlineimap to mbsync, I > guess the issues would be the same. I wonder if the thing to do would be to write an mbsync-specific utility to convert IMAP uids to notmuch properties and back. Then maybe I could extend muchsync to sync properties (which it currently ignores because I wrote muchsync before properties existed, and still don't really know what properties are good for). A problem with syncing properties, though, is that I don't know how to do conflict resolution correctly 100% of the time. One of the key insights behind muchsync is that with file names and binary flags, I think I figured out a sane way of resolving all conflicts without involving the user (namely take the max number of links in each directory with special treatment for new/ and cur/, then logically and the muchsync.and_tags, and logically or the other tags). With properties, it's not clear how to sync them generically. Moreover, some properties like session-key probably should not be synced, since you probably don't want to upload the equivalent of plaintext main messages to your mail server. David _______________________________________________ notmuch mailing list notmuch@notmuchmail.org https://notmuchmail.org/mailman/listinfo/notmuch