Re: gmail label support in offlineimap - update
authorJeremy Nickurak <not-much@trk.nickurak.ca>
Wed, 28 Nov 2012 16:46:52 +0000 (09:46 +1700)
committerW. Trevor King <wking@tremily.us>
Fri, 7 Nov 2014 17:51:07 +0000 (09:51 -0800)
56/8a8e5e11569cecaa803b78ee2dd1bccabf3119 [new file with mode: 0644]

diff --git a/56/8a8e5e11569cecaa803b78ee2dd1bccabf3119 b/56/8a8e5e11569cecaa803b78ee2dd1bccabf3119
new file mode 100644 (file)
index 0000000..cfa35ac
--- /dev/null
@@ -0,0 +1,116 @@
+Return-Path: <jeremy@nickurak.ca>\r
+X-Original-To: notmuch@notmuchmail.org\r
+Delivered-To: notmuch@notmuchmail.org\r
+Received: from localhost (localhost [127.0.0.1])\r
+       by olra.theworths.org (Postfix) with ESMTP id C5714431FAF\r
+       for <notmuch@notmuchmail.org>; Wed, 28 Nov 2012 08:46:56 -0800 (PST)\r
+X-Virus-Scanned: Debian amavisd-new at olra.theworths.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: -0.699\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=-0.699 tagged_above=-999 required=5\r
+       tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001,\r
+       RCVD_IN_DNSWL_LOW=-0.7] autolearn=disabled\r
+Received: from olra.theworths.org ([127.0.0.1])\r
+       by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)\r
+       with ESMTP id yPFsmHk4Gl0y for <notmuch@notmuchmail.org>;\r
+       Wed, 28 Nov 2012 08:46:55 -0800 (PST)\r
+Received: from mail-lb0-f181.google.com (mail-lb0-f181.google.com\r
+       [209.85.217.181]) (using TLSv1 with cipher RC4-SHA (128/128 bits))\r
+       (No client certificate requested)\r
+       by olra.theworths.org (Postfix) with ESMTPS id C5E4C431FAE\r
+       for <notmuch@notmuchmail.org>; Wed, 28 Nov 2012 08:46:54 -0800 (PST)\r
+Received: by mail-lb0-f181.google.com with SMTP id ge1so11560683lbb.26\r
+       for <notmuch@notmuchmail.org>; Wed, 28 Nov 2012 08:46:53 -0800 (PST)\r
+DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;\r
+       d=nickurak.ca; s=google-dkim;\r
+       h=mime-version:sender:x-originating-ip:in-reply-to:references:date\r
+       :x-google-sender-auth:message-id:subject:from:to:content-type;\r
+       bh=CMYJFpfRqZYARYdToqREEkiziommepK63U7Qqxphqk8=;\r
+       b=YwiqIEYuxmGyBaQJ6JL//IbHWcukSfn/zYV218Bb7oNBrKMuUa+3NBzcjNsXCQSWto\r
+       KM/nuw+h+VINCbCb4PpY5VYDL6BHWqfZyJLLPDFQhX8tntwaNB5lLzftCHolbZQ81iR7\r
+       Up0MGWAeDmJ4c1jb4b78Fq4KKVinnjS8nXi9c=\r
+X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;\r
+       d=google.com; s=20120113;\r
+       h=mime-version:sender:x-originating-ip:in-reply-to:references:date\r
+       :x-google-sender-auth:message-id:subject:from:to:content-type\r
+       :x-gm-message-state;\r
+       bh=CMYJFpfRqZYARYdToqREEkiziommepK63U7Qqxphqk8=;\r
+       b=llxSmOLlv7p5yRUB/1NAVrsjXNOyro03UjRRw7E5+G+5kJ2qmBbN3PBVI/AzVzaKJd\r
+       3RVyxRKrgyLJmzsDiBm6BLGMaIZ8JQG/4dEDZ92ja1S+9BX1P8UQEfnejVnoykEmod06\r
+       KvzMxmTf0nWXEXk0f13x9E+5lqtsqzCsDPSnaNqlejWpeJlFZz95POH3q/2KdA97phR7\r
+       FMDIQgWaFUSUMdAW0/OnLiXctkmlDzXiX3yJl8TevYKlTvLE++qY+1+9UI600ce7qR+r\r
+       oj6PlDUq39W5q9yKq9Y320IxmgiGCgYIIldmgJD+YaGSV3LikAYu0hZ3eTMN/muS0Hsm\r
+       ijag==\r
+MIME-Version: 1.0\r
+Received: by 10.112.31.194 with SMTP id c2mr8066905lbi.44.1354121213189; Wed,\r
+       28 Nov 2012 08:46:53 -0800 (PST)\r
+Sender: jeremy@nickurak.ca\r
+Received: by 10.114.37.71 with HTTP; Wed, 28 Nov 2012 08:46:52 -0800 (PST)\r
+X-Originating-IP: [68.148.28.35]\r
+In-Reply-To: <50B62409.7050706@gmail.com>\r
+References: <50B62409.7050706@gmail.com>\r
+Date: Wed, 28 Nov 2012 09:46:52 -0700\r
+X-Google-Sender-Auth: JMqwvr5hkSwYX_ZHK-kSft5QFcc\r
+Message-ID:\r
+ <CA+eQo_0wOSjHoMK30_PwGZonBNbSDCRy+ghX-TnimfZp++8cBg@mail.gmail.com>\r
+Subject: Re: gmail label support in offlineimap - update\r
+From: Jeremy Nickurak <not-much@trk.nickurak.ca>\r
+To: notmuch <notmuch@notmuchmail.org>\r
+Content-Type: multipart/alternative; boundary=f46d04016951e51ed904cf90e9f9\r
+X-Gm-Message-State:\r
+ ALoCoQmVZMgJjJUSerLFNArTGUWRbeSDshnoxcKRKdW4coI0nX/lTagNJbEW8TFvLJ9OEQhYGnVu\r
+X-BeenThere: notmuch@notmuchmail.org\r
+X-Mailman-Version: 2.1.13\r
+Precedence: list\r
+List-Id: "Use and development of the notmuch mail system."\r
+       <notmuch.notmuchmail.org>\r
+List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,\r
+       <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>\r
+List-Archive: <http://notmuchmail.org/pipermail/notmuch>\r
+List-Post: <mailto:notmuch@notmuchmail.org>\r
+List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>\r
+List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,\r
+       <mailto:notmuch-request@notmuchmail.org?subject=subscribe>\r
+X-List-Received-Date: Wed, 28 Nov 2012 16:46:56 -0000\r
+\r
+--f46d04016951e51ed904cf90e9f9\r
+Content-Type: text/plain; charset=UTF-8\r
+\r
+As far as syncing flags to notmuch, it sounds like this would be easy to\r
+achieve with an independent 3rd tool, or even a small script:\r
+1) Find files in the maildir modified since the last check\r
+2) Read their keywords headers\r
+3) Update the notmuch tags accordingnly.\r
+\r
+The other direction sounds like it would be trickier though, since there's\r
+no obvious way to say "what notmuch tags have changed since time X?". Is\r
+this something that notmuch could provide?\r
+\r
+Alternatively, would it be a good idea to give notmuch a tags-changed hook,\r
+so that an external tool could be called on a tag change? That sounds like\r
+would solve this problem, keep the gmail/imap logic safely away from\r
+notmuch, and probably provide some really interesting other opportunities\r
+for automation of things by tags.\r
+\r
+--f46d04016951e51ed904cf90e9f9\r
+Content-Type: text/html; charset=UTF-8\r
+Content-Transfer-Encoding: quoted-printable\r
+\r
+As far as syncing flags to notmuch, it sounds like this would be easy to ac=\r
+hieve with an independent 3rd tool, or even a small script:<div>1) Find fil=\r
+es in the maildir modified since the last check</div><div>2) Read their key=\r
+words headers</div>\r
+\r
+<div>3) Update the notmuch tags accordingnly.</div><div><br></div><div>The =\r
+other direction sounds like it would be trickier though, since there&#39;s =\r
+no obvious way to say &quot;what notmuch tags have changed since time X?&qu=\r
+ot;. Is this something that notmuch could provide?</div>\r
+<div><br></div><div>Alternatively, would it be a good idea to give notmuch =\r
+a tags-changed hook, so that an external tool could be called on a tag chan=\r
+ge? That sounds like would solve this problem, keep the gmail/imap logic sa=\r
+fely away from notmuch, and probably provide some really interesting other =\r
+opportunities for automation of things by tags.</div>\r
+\r
+\r
+--f46d04016951e51ed904cf90e9f9--\r