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