Re: [PATCH/RFC 0/3] Maildir custom flags and notmuch tags

diff --git a/89/42dd66239abe5809cb97cd3dfccbff9d0bce07 b/89/42dd66239abe5809cb97cd3dfccbff9d0bce07
new file mode 100644 (file)
index 0000000..77040cc
--- /dev/null
+++ b/89/42dd66239abe5809cb97cd3dfccbff9d0bce07
@@ -0,0 +1,83 @@
+Return-Path: <ccx@webprojekty.cz>\r
+X-Original-To: notmuch@notmuchmail.org\r
+Delivered-To: notmuch@notmuchmail.org\r
+Received: from localhost (localhost [127.0.0.1])\r
+ by arlo.cworth.org (Postfix) with ESMTP id 066F06DE1226\r
+ for <notmuch@notmuchmail.org>; Tue,  2 Feb 2016 08:58:59 -0800 (PST)\r
+X-Virus-Scanned: Debian amavisd-new at cworth.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: 0\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[none]\r
+ autolearn=disabled\r
+Received: from arlo.cworth.org ([127.0.0.1])\r
+ by localhost (arlo.cworth.org [127.0.0.1]) (amavisd-new, port 10024)\r
+ with ESMTP id BeliTkVDw3fe for <notmuch@notmuchmail.org>;\r
+ Tue,  2 Feb 2016 08:58:56 -0800 (PST)\r
+X-Greylist: delayed 389 seconds by postgrey-1.35 at arlo;\r
+ Tue, 02 Feb 2016 08:58:56 PST\r
+Received: from ccx.webprojekty.cz (156.200.broadband11.iol.cz\r
+ [90.178.200.156]) by arlo.cworth.org (Postfix) with ESMTP id 19AE26DE01FF for\r
+ <notmuch@notmuchmail.org>; Tue,  2 Feb 2016 08:58:55 -0800 (PST)\r
+Received: from dorje.v103.te2000 (unknown [82.142.125.46])\r
+ (Authenticated sender: ccx@webprojekty.cz)\r
+ by ccx.webprojekty.cz (Postfix) with ESMTPSA id 70D901176\r
+ for <notmuch@notmuchmail.org>; Tue,  2 Feb 2016 17:01:00 +0100 (CET)\r
+Date: Tue, 2 Feb 2016 17:52:20 +0100\r
+From: Jan Pobrislo <ccx@webprojekty.cz>\r
+To: notmuch@notmuchmail.org\r
+Subject: Re: [PATCH/RFC 0/3] Maildir custom flags and notmuch tags\r
+Message-ID: <20160202175220.12f8a712@dorje.v103.te2000>\r
+In-Reply-To: <87mvsd7cxr.fsf@zancas.localnet>\r
+References: <1448504191-30974-1-git-send-email-igor.contato@gmail.com>\r
+ <87mvsd7cxr.fsf@zancas.localnet>\r
+X-Mailer: Claws Mail 3.13.0 (GTK+ 2.24.28; x86_64-pc-linux-gnu)\r
+MIME-Version: 1.0\r
+Content-Type: text/plain; charset=US-ASCII\r
+Content-Transfer-Encoding: 7bit\r
+X-BeenThere: notmuch@notmuchmail.org\r
+X-Mailman-Version: 2.1.20\r
+Precedence: list\r
+List-Id: "Use and development of the notmuch mail system."\r
+ <notmuch.notmuchmail.org>\r
+List-Unsubscribe: <https://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: <https://notmuchmail.org/mailman/listinfo/notmuch>,\r
+ <mailto:notmuch-request@notmuchmail.org?subject=subscribe>\r
+X-List-Received-Date: Tue, 02 Feb 2016 16:58:59 -0000\r
+\r
+Hello. I've been thinking about this feature for quite some while.\r
+Having tags stored and synchronized together with mail would certainly\r
+make life easier for a lot of notmuch user. And the upside is that you\r
+can already do that with Dovecot's dsync tool.\r
+\r
+But from what I've seen in the patches (as far as I understood them) it\r
+doesn't really work anything like keyword storage in Dovecot - aside\r
+from using maildir flags a-z.\r
+\r
+I've been missing comprehensive source of information on various things\r
+maildir-related, so I've written this: https://notmuchmail.org/software/\r
+It includes links to specifications of the two keyword storage formats\r
+for maildir: Dovecot's and Courier's. There's a lot more that can be\r
+added on that page, all the MUAs for starters.\r
+\r
+I think that using fixed mapping for flag meaning is a good POC step,\r
+but that won't work without explicit support from the synchronizer to\r
+map specific keywords to always same tags. I don't really know what\r
+offlineimap does to synchronize keywords, if anything. Dsync already\r
+does what it does - which is obviously to use the full dovecot format.\r
+\r
+Having the mapping in the maildir rather than database can work well\r
+because you have one unambiguous format that both synchronizer and\r
+notmuch can use without much hassle. And it will scale up to 26\r
+different tags per maildir, after that it will unfortunately stop\r
+working without resorting to dovecot-specific formats, but I think it\r
+still covers 98% of use-cases or so.\r
+\r
+On the other hand, you can hack up a script that renames mail\r
+post-dsync to conform to expected static mapping. The change detection\r
+with just one auxiliary file is simple too, as opposed to the\r
+subdirectory format Courier uses.\r