From 555d55c9b17b0de305e7bc52978e267b8fa0e8bb Mon Sep 17 00:00:00 2001 From: David Mazieres Date: Sat, 12 Apr 2014 11:02:01 +1700 Subject: [PATCH] Re: Synchronization success stories? --- 0c/16e1e7f87bbbeb614cbb0c75dcd9701a0c0686 | 86 +++++++++++++++++++++++ 1 file changed, 86 insertions(+) create mode 100644 0c/16e1e7f87bbbeb614cbb0c75dcd9701a0c0686 diff --git a/0c/16e1e7f87bbbeb614cbb0c75dcd9701a0c0686 b/0c/16e1e7f87bbbeb614cbb0c75dcd9701a0c0686 new file mode 100644 index 000000000..1713147f3 --- /dev/null +++ b/0c/16e1e7f87bbbeb614cbb0c75dcd9701a0c0686 @@ -0,0 +1,86 @@ +Return-Path: + +X-Original-To: notmuch@notmuchmail.org +Delivered-To: notmuch@notmuchmail.org +Received: from localhost (localhost [127.0.0.1]) + by olra.theworths.org (Postfix) with ESMTP id 1D26141ED76 + for ; Fri, 11 Apr 2014 11:02:12 -0700 (PDT) +X-Virus-Scanned: Debian amavisd-new at olra.theworths.org +X-Spam-Flag: NO +X-Spam-Score: -2.3 +X-Spam-Level: +X-Spam-Status: No, score=-2.3 tagged_above=-999 required=5 + tests=[RCVD_IN_DNSWL_MED=-2.3] autolearn=disabled +Received: from olra.theworths.org ([127.0.0.1]) + by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024) + with ESMTP id JZ-lKtIoGQFE for ; + Fri, 11 Apr 2014 11:02:04 -0700 (PDT) +Received: from market.scs.stanford.edu (market.scs.stanford.edu [171.66.3.10]) + (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) + (No client certificate requested) + by olra.theworths.org (Postfix) with ESMTPS id DCC7241ED71 + for ; Fri, 11 Apr 2014 11:02:03 -0700 (PDT) +Received: from market.scs.stanford.edu (localhost.scs.stanford.edu + [127.0.0.1]) by market.scs.stanford.edu (8.14.7/8.14.7) with ESMTP id + s3BI21YI017924; Fri, 11 Apr 2014 11:02:01 -0700 (PDT) +Received: (from dm@localhost) + by market.scs.stanford.edu (8.14.7/8.14.7/Submit) id s3BI218D017688; + Fri, 11 Apr 2014 11:02:01 -0700 (PDT) +X-Authentication-Warning: market.scs.stanford.edu: dm set sender to + return-38na78y6wrihpayyrtsewvtyin@ta.scs.stanford.edu using -f +From: David Mazieres +To: David Bremner , Brian Sniffen , + notmuch@notmuchmail.org +Subject: Re: Synchronization success stories? +In-Reply-To: <87d2go5cyr.fsf@zancas.localnet> +References: + <87d2go5cyr.fsf@zancas.localnet> +Date: Fri, 11 Apr 2014 11:02:01 -0700 +Message-ID: <8738hj3fty.fsf@ta.scs.stanford.edu> +MIME-Version: 1.0 +Content-Type: text/plain +X-BeenThere: notmuch@notmuchmail.org +X-Mailman-Version: 2.1.13 +Precedence: list +Reply-To: David Mazieres expires 2014-07-10 PDT + +List-Id: "Use and development of the notmuch mail system." + +List-Unsubscribe: , + +List-Archive: +List-Post: +List-Help: +List-Subscribe: , + +X-List-Received-Date: Fri, 11 Apr 2014 18:02:12 -0000 + +David Bremner writes: + +> Brian Sniffen writes: +> +>> I'm thrilled by using notmuch to manage my mail. Low-latency search is +>> very important to me. But I use computers in a couple of +>> places---several of which are laptops. Has anyone stories to share of +>> successful multi-computer notmuch sync, for a corpus of a +>> quarter-million messages or so? +> +> I use syncmaildir to sync the actual messages, and a copy of the output +> of "notmuch dump" in git to sync the metadata. +> +> It works OK. A bit slow; depends how often you need to fetch new mail. + +If you want to see my solution, it is here: + + http://www.scs.stanford.edu/~dm/muchsync-0.tar.gz + +I'm a little embarrassed by this code, as I just started to test it a +week ago then instantly became completely dependent on it. I will +probably change the name (from muchsync to syncmuch) and the database +format before releasing. But if you feel like beta-testing and giving +me feedback, have a look. + +Beware that if you have been using notmuch dump, you may become +instantly hooked on my solution... + +David -- 2.26.2