From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from localhost (localhost [127.0.0.1]) by arlo.cworth.org (Postfix) with ESMTP id F25136DE01F5 for ; Wed, 9 Jan 2019 09:23:39 -0800 (PST) X-Virus-Scanned: Debian amavisd-new at cworth.org X-Spam-Flag: NO X-Spam-Score: -2.171 X-Spam-Level: X-Spam-Status: No, score=-2.171 tagged_above=-999 required=5 tests=[AWL=0.230, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=disabled Received: from arlo.cworth.org ([127.0.0.1]) by localhost (arlo.cworth.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XcR1WVyYXAZ4 for ; Wed, 9 Jan 2019 09:23:38 -0800 (PST) X-Greylist: delayed 1978 seconds by postgrey-1.36 at arlo; Wed, 09 Jan 2019 09:23:37 PST Received: from market.scs.stanford.edu (market.scs.stanford.edu [171.66.3.10]) by arlo.cworth.org (Postfix) with ESMTPS id 472476DE018C for ; Wed, 9 Jan 2019 09:23:37 -0800 (PST) Received: from market.scs.stanford.edu (localhost [127.0.0.1]) by market.scs.stanford.edu (8.16.0.29/8.16.0.21) with ESMTP id x09GoULL041534; Wed, 9 Jan 2019 08:50:30 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=scs.stanford.edu; s=scs; t=1547052630; bh=MtzpAntYE/WldEJjlnCJcU9Bw/XyvT8+ZtDrbgfM6PU=; h=From:To:Subject:In-Reply-To:References:Date:Message-ID: MIME-Version; b=VHVbBTQ8x34O3LkKc5WE5J1cOMv4gZsTvTmuc/y+MG8lAFU64+EZKntnZ5B5JETfJ y5z4TH1FHi+3qrlNSFoNaBnuecpBB9u1tVKSzcllIuWAT3Px4TsX3FhI3eyKKGT2X7 VSt7QFNNo2oHf9MwqPbE/DF1oQqB7dT3VvFR0bI0= Received: (from dm@localhost) by market.scs.stanford.edu (8.16.0.29/8.16.0.29/Submit) id x09GoRH0053409; Wed, 9 Jan 2019 08:50:27 -0800 (PST) From: David Mazieres To: Jeff Templon , Dan =?utf-8?B?xIxlcm3DoWs=?= , notmuch@notmuchmail.org Subject: Re: How do you synchronize your notmuch tags across multiple machines? In-Reply-To: References: <87d0pzwykt.fsf@cgc-instruments.com> <87mup3bqmh.fsf@ra.horus-it.com> <8636qv5juu.fsf@lama-e29.univ-savoie.fr> <87pntd74wt.fsf@cgc-instruments.com> <87imz47d2s.fsf@cgc-instruments.com> <87a7keifhh.fsf@ta.scs.stanford.edu> <87sgy24sfb.fsf@cgc-instruments.com> <87tvii6xpt.fsf@ta.scs.stanford.edu> Reply-To: David Mazieres expires 2019-04-09 PDT Date: Wed, 09 Jan 2019 08:50:21 -0800 Message-ID: <87a7k9u65u.fsf@ta.scs.stanford.edu> MIME-Version: 1.0 Content-Type: text/plain X-BeenThere: notmuch@notmuchmail.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Use and development of the notmuch mail system." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Jan 2019 17:23:40 -0000 Jeff Templon 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