--- /dev/null
+Return-Path: <m.walters@qmul.ac.uk>\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 1DD1C431E82\r
+ for <notmuch@notmuchmail.org>; Sat, 3 May 2014 00:12:09 -0700 (PDT)\r
+X-Virus-Scanned: Debian amavisd-new at olra.theworths.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: 0.502\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=0.502 tagged_above=-999 required=5\r
+ tests=[DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001,\r
+ NML_ADSP_CUSTOM_MED=1.2, 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 mcFlvcYeaDTN for <notmuch@notmuchmail.org>;\r
+ Sat, 3 May 2014 00:12:01 -0700 (PDT)\r
+Received: from mail2.qmul.ac.uk (mail2.qmul.ac.uk [138.37.6.6])\r
+ (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))\r
+ (No client certificate requested)\r
+ by olra.theworths.org (Postfix) with ESMTPS id C1740431E62\r
+ for <notmuch@notmuchmail.org>; Sat, 3 May 2014 00:12:00 -0700 (PDT)\r
+Received: from smtp.qmul.ac.uk ([138.37.6.40])\r
+ by mail2.qmul.ac.uk with esmtp (Exim 4.71)\r
+ (envelope-from <m.walters@qmul.ac.uk>)\r
+ id 1WgU6x-00035V-Pz; Sat, 03 May 2014 08:11:55 +0100\r
+Received: from 5751dfa2.skybroadband.com ([87.81.223.162] helo=localhost)\r
+ by smtp.qmul.ac.uk with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.71)\r
+ (envelope-from <m.walters@qmul.ac.uk>)\r
+ id 1WgU6x-0004q8-Fb; Sat, 03 May 2014 08:11:51 +0100\r
+From: Mark Walters <markwalters1009@gmail.com>\r
+To: David Mazieres expires 2014-07-31 PDT\r
+ <mazieres-dznikihr9t4gcgb72gnhf9954a@temporary-address.scs.stanford.edu>,\r
+ Jani Nikula <jani@nikula.org>\r
+Subject: Re: folder and path completely broken in HEAD?\r
+In-Reply-To: <87oazfo3w2.fsf@ta.scs.stanford.edu>\r
+References: <87oazfo3w2.fsf@ta.scs.stanford.edu>\r
+User-Agent: Notmuch/0.15.2+615~g78e3a93 (http://notmuchmail.org) Emacs/23.4.1\r
+ (x86_64-pc-linux-gnu)\r
+Date: Sat, 03 May 2014 08:11:50 +0100\r
+Message-ID: <87zjiz8hft.fsf@qmul.ac.uk>\r
+MIME-Version: 1.0\r
+Content-Type: text/plain; charset=us-ascii\r
+X-Sender-Host-Address: 87.81.223.162\r
+X-QM-Geographic: According to ripencc,\r
+ this message was delivered by a machine in Britain (UK) (GB).\r
+X-QM-SPAM-Info: Sender has good ham record. :)\r
+X-QM-Body-MD5: 7129430a0d3ec8ecc226dc40ce18c7d8 (of first 20000 bytes)\r
+X-SpamAssassin-Score: -0.1\r
+X-SpamAssassin-SpamBar: /\r
+X-SpamAssassin-Report: The QM spam filters have analysed this message to\r
+ determine if it is\r
+ spam. We require at least 5.0 points to mark a message as spam.\r
+ This message scored -0.1 points.\r
+ Summary of the scoring: \r
+ * 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail\r
+ provider * (markwalters1009[at]gmail.com)\r
+ * -0.1 AWL AWL: From: address is in the auto white-list\r
+X-QM-Scan-Virus: ClamAV says the message is clean\r
+Cc: notmuch@notmuchmail.org\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: Sat, 03 May 2014 07:12:09 -0000\r
+\r
+\r
+On Sat, 03 May 2014, dm-list-email-notmuch@scs.stanford.edu wrote:\r
+> Jani Nikula <jani@nikula.org> writes:\r
+>\r
+>> On Fri, 02 May 2014, dm-list-email-notmuch@scs.stanford.edu wrote:\r
+>>>\r
+>>> I'm using a pretty standard maildir++ layout. For example, underneath\r
+>>> my database.path I have a bunch of mail in directories such as:\r
+>>>\r
+>>> .INBOX.Main/{new,cur}\r
+>>> .mail.class/{new,cur}\r
+>>> .mail.voicemail/{new,cur}\r
+>>> ...\r
+>> Here's additional commentary on the specific queries.\r
+>>\r
+>>> linux7$ ./notmuch count folder:mail\r
+>>> 0\r
+>>> linux8$ ./notmuch count folder:.mail\r
+>>> 0\r
+>\r
+> Oh, man. That's a serious bummer.\r
+>\r
+> Is there any mechanism left that would let me hierarchically group\r
+> messages? I've got a ton of mail.* folders, and create new ones\r
+> dynamically. I really want a mechanism to group them hierarchically, so\r
+> I can have a search that matches all current and future mail\r
+> directories. I organized my whole mail setup around folders because a)\r
+> tags do not provide this kind of hierarchical control, and b) there\r
+> doesn't seem to be a convenient way to apply tags 100% reliably on\r
+> message delivery, whereas I *can* control the folder 100% reliably.\r
+>\r
+> Worse, because of my poor performance, I was hoping to segregate\r
+> messages by year. So it would be:\r
+>\r
+> 2013/.mail.class\r
+> 2013/.mail.voicemail\r
+> 2014/.mail.class\r
+> 2014/.mail.voicemail\r
+>\r
+> All the way back. Now you are saying there will be no convenient way to\r
+> match just the "mail.class" part without the year? How very\r
+> distressing. Ugh.\r
+\r
+Hi\r
+\r
+I am not quite sure what you are meaning by hierarchically group\r
+messages. Searching for path:dir/foo/bar/** should give all messages in\r
+all directories beneath dir/foo/bar. \r
+\r
+So for the year example you give you could have directories\r
+mail/class/2013 and mail/class/2014/ etc. \r
+\r
+Anyway if you can describe your use more fully we may be able to\r
+help. And if it can't do what you want it would also give us some idea\r
+of what would need to be changed.\r
+\r
+Finally, I am not quite sure what this means\r
+\r
+> there doesn't seem to be a convenient way to apply tags 100% reliably\r
+> on message delivery, whereas I *can* control the folder 100% reliably.\r
+\r
+Are you wanting to tag messages based on some properties when doing\r
+notmuch new while avoiding races etc? Or are you worried about duplicate\r
+message-ids? Or something else?\r
+\r
+Best wishes\r
+\r
+Mark\r
+\r
+\r
+\r
+\r
+>\r
+> David\r
+> _______________________________________________\r
+> notmuch mailing list\r
+> notmuch@notmuchmail.org\r
+> http://notmuchmail.org/mailman/listinfo/notmuch\r
projects / notmuch-archives.git / commitdiff