From d30489dff3da7c55059252c470095d720315cb82 Mon Sep 17 00:00:00 2001 From: David Mazieres expires 2014-07-26 PDT Date: Mon, 28 Apr 2014 12:45:23 +1700 Subject: [PATCH] Re: github mirror --- 23/14effa2ee7d74a54235c915ef12e9e957e6c18 | 90 +++++++++++++++++++++++ 1 file changed, 90 insertions(+) create mode 100644 23/14effa2ee7d74a54235c915ef12e9e957e6c18 diff --git a/23/14effa2ee7d74a54235c915ef12e9e957e6c18 b/23/14effa2ee7d74a54235c915ef12e9e957e6c18 new file mode 100644 index 000000000..dfe7be452 --- /dev/null +++ b/23/14effa2ee7d74a54235c915ef12e9e957e6c18 @@ -0,0 +1,90 @@ +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 D4576431FBD + for ; Sun, 27 Apr 2014 12:45:32 -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 baauO2Ph4K7P for ; + Sun, 27 Apr 2014 12:45:29 -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 EA74B431FBC + for ; Sun, 27 Apr 2014 12:45:28 -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 + s3RJjQDk013208; Sun, 27 Apr 2014 12:45:26 -0700 (PDT) +Received: (from dm@localhost) + by market.scs.stanford.edu (8.14.7/8.14.7/Submit) id s3RJjQBJ030412; + Sun, 27 Apr 2014 12:45:26 -0700 (PDT) +X-Authentication-Warning: market.scs.stanford.edu: dm set sender to + return-u67pwu3kqu6hnfzyisgadfg85i@ta.scs.stanford.edu using -f +From: David Mazieres expires 2014-07-26 PDT + +To: Sam Halliday , notmuch@notmuchmail.org +Subject: Re: github mirror +In-Reply-To: <8761lulg8i.fsf@Samskara.home> +References: <87bnvn111h.fsf@Samskara.home> + <87iopu4mr6.fsf@ta.scs.stanford.edu> <8761lulg8i.fsf@Samskara.home> +Date: Sun, 27 Apr 2014 12:45:23 -0700 +Message-ID: <87d2g24kvg.fsf@ta.scs.stanford.edu> +MIME-Version: 1.0 +Content-Type: text/plain +X-Mailman-Approved-At: Wed, 30 Apr 2014 01:31:08 -0700 +X-BeenThere: notmuch@notmuchmail.org +X-Mailman-Version: 2.1.13 +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: Sun, 27 Apr 2014 19:45:33 -0000 + +Sam Halliday writes: + +> David Mazieres writes: +>> The problem is that different imap servers store tags in different +>> ways. Since notmuch does not use imap, it would be hard for notmuch to +>> synchronize the tags, other than the standard ones (for which notmuch +>> already has support). +>> +>> One thing you could do is build an external tool that synchronizes +>> notmuch tags and spawns an imap server in preauth mode to sync the tags. +>> (That would be yet another use for the ctime values we have discussed on +>> this list.) +> +> The improvements to offlineimap to use the mail header hack might work +> well for both of us. Currently the only way to add/remove "labels" (a +> gmail concept) is to copy/move mail between folders. And this is how +> notmuch "tags" are synced. But with outstanding pull request, this can +> all be managed via email headers and that means you *only* need to +> synchronise your "All Mail" folder. +> +> So, I'd be interested to see what your code could do in that world :-) + +My code assumes shell access to your mail server, so it doesn't do squat +in the gmail world. I suppose you could use gmail just as your SMTP +server, then download everything to your own server with offlineimap and +manage it with notmuch there, in which case my code gives you the +notmuch experience on all your devices. However, there's a much better +SMTP server out than what google is running (www.mailavenger.org), so +such a setups is backwards... The right thing to do is to receive +everything on a mail server that you control, then push to gmail only +what you want to read on your phone and/or disclose to the NSA (which in +my case is only a tiny fraction of my email). + +David -- 2.26.2