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 47BA46DE0244 for ; Thu, 3 Jan 2019 14:55:24 -0800 (PST) X-Virus-Scanned: Debian amavisd-new at cworth.org X-Spam-Flag: NO X-Spam-Score: -0.1 X-Spam-Level: X-Spam-Status: No, score=-0.1 tagged_above=-999 required=5 tests=[AWL=0.100, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, MIME_QP_LONG_LINE=0.001, 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 V9_6uv0CMcjO for ; Thu, 3 Jan 2019 14:55:23 -0800 (PST) X-Greylist: delayed 391 seconds by postgrey-1.36 at arlo; Thu, 03 Jan 2019 14:55:22 PST Received: from istari.evenmere.org (istari.evenmere.org [136.248.125.194]) by arlo.cworth.org (Postfix) with ESMTP id D4CB46DE014D for ; Thu, 3 Jan 2019 14:55:22 -0800 (PST) Received: by istari.evenmere.org (Postfix, from userid 113) id 6F9B41F7DC6; Thu, 3 Jan 2019 17:48:46 -0500 (EST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=evenmere.org; s=default; t=1546555726; bh=iloZ4RkXaWC1iai5CmyL7rXHBQ9dfGdVb42Q41UtjEo=; h=Subject:From:In-Reply-To:Date:Cc:References:To:From; b=FLwgh9VlitKJmcq9kGwXNaYWy1L1y2VvH37zWvUVGbusYZtUw9i2RfpT5+ORUIHiY pUXdCf1emo7TwpW48z6VmvNHNzkzi6e2GTUO1Rw5Gh9XLaZc+6k+xP1PYTubIKo5kz jazn1qZQeA0uM9DwCfJFV3a/1j5qzyMTlIvguaTA= Received: from [IPv6:2001:4878:a000:3000:3543:5778:92f6:a0cc] (unknown [IPv6:2001:4878:a000:3000:3543:5778:92f6:a0cc]) by istari.evenmere.org (Postfix) with ESMTPSA id 424A31F7DA9; Thu, 3 Jan 2019 17:48:44 -0500 (EST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=evenmere.org; s=default; t=1546555724; bh=iloZ4RkXaWC1iai5CmyL7rXHBQ9dfGdVb42Q41UtjEo=; h=Subject:From:In-Reply-To:Date:Cc:References:To:From; b=JIqZqeC6Psy6gkac3ZhFCsmNQVLB9s4INuG5x/9dksL8ebLKus4fH+QxDDLVxCGks w9CTU78PawTpee4G7pIQPdMXBVazsuci+gJcghIEDYq4Hzp5N2WdV6oZ+d2y7lygnS ZFtCXDIpJHRbNgQ01FktBEPEmqfbYmZ60yIC6H/s= Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (1.0) Subject: Re: How do you synchronize your notmuch tags across multiple machines? From: Brian Sniffen X-Mailer: iPhone Mail (16C101) In-Reply-To: <87pntd74wt.fsf@cgc-instruments.com> Date: Thu, 3 Jan 2019 17:48:42 -0500 Cc: notmuch@notmuchmail.org Content-Transfer-Encoding: quoted-printable Message-Id: References: <87d0pzwykt.fsf@cgc-instruments.com> <87mup3bqmh.fsf@ra.horus-it.com> <8636qv5juu.fsf@lama-e29.univ-savoie.fr> <87pntd74wt.fsf@cgc-instruments.com> To: =?utf-8?Q?Dan_=C4=8Cerm=C3=A1k?= 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: Thu, 03 Jan 2019 22:55:24 -0000 I had the same problem. I found a solution: dispense with imap. This can be i= n two ways: For work, I use getmail (and imap) to read messages from an Exchange server a= nd drop them in a maildir. Muchsync then coordinates those.=20 For personal mail, I just use muchsync to directly manipulate Dovecot=E2=80=99= s maildir.=20 Both work fine. In the =E2=80=9Cwork=E2=80=9D case, changes are not pushed b= ack up to the server.=20 --=20 Brian Sniffen > On Jan 3, 2019, at 5:27 PM, Dan =C4=8Cerm=C3=A1k w= rote: >=20 > I have just given muchsync a try and it synchronizes email and tags very > quickly. I am quite impressed by it! >=20 > Unfortunately, I have hit exactly the same problem that you describe: I > have to have a single machine that pulls in my email via offlineimap and > then sync to the others via muchsync. That is a little inconvenient, as > I was hoping that I could switch the "master" depending on which machine > I am currently using and not having it up and online at all times. >=20 > I am afraid that that's not going to be easy to accomplish, as it > requires muchsync and a maildir synchronization program (in my case > offlineimap) to play together. The problem with offlineimap seems to be > that it expects the maildir filenames to have a different form and does > not recognize those that muchsync created (and it instead tries to clone > all my inboxes again). In case I'll manage to get muchsync to work > without a dedicated master, I'll let the list know. >=20 >=20 > Cheers, >=20 > Dan >=20 > Tom Hirschowitz writes: >=20 >> I also use muchsync. Had a few issues with it in the beginning but the >> author, David Mazi=C3=A8res, was quite efficient in fixing them, and pati= ent >> with me being awkwardly incompetent. It's been working like a charm >> since then. >>=20 >> It took me some time to figure out a working set up though. My mail is >> now fetched first on the same machine everytime, and then synchronised >> from other machines through muchsync. This is a bit annoying, and I'd be >> curious if anyone had a better way. >>=20 >> Tom >>=20 >>> * Dan =C4=8Cerm=C3=A1k: >>>=20 >>>> I have found muchsync, but unfortunately very little reports about how >>>> well it works, which isn't necessarily a bad thing. >>>=20 >>> Muchsync works well for me, although I only need to sync between two >>> machines. It is quite fast after the initial synchronisation, and I >>> did not have any problems yet. I reported a small error in the >>> documentation, but that should be fixed by now. >>>=20 >>> -Ralph >>> _______________________________________________ >>> notmuch mailing list >>> notmuch@notmuchmail.org >>> https://notmuchmail.org/mailman/listinfo/notmuch >> _______________________________________________ >> notmuch mailing list >> notmuch@notmuchmail.org >> https://notmuchmail.org/mailman/listinfo/notmuch > _______________________________________________ > notmuch mailing list > notmuch@notmuchmail.org > https://notmuchmail.org/mailman/listinfo/notmuch