1 Return-Path: <m.walters@qmul.ac.uk>
\r
2 X-Original-To: notmuch@notmuchmail.org
\r
3 Delivered-To: notmuch@notmuchmail.org
\r
4 Received: from localhost (localhost [127.0.0.1])
\r
5 by olra.theworths.org (Postfix) with ESMTP id 46D82431E82
\r
6 for <notmuch@notmuchmail.org>; Sat, 3 May 2014 11:57:37 -0700 (PDT)
\r
7 X-Virus-Scanned: Debian amavisd-new at olra.theworths.org
\r
11 X-Spam-Status: No, score=0.502 tagged_above=-999 required=5
\r
12 tests=[DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001,
\r
13 NML_ADSP_CUSTOM_MED=1.2, RCVD_IN_DNSWL_LOW=-0.7] autolearn=disabled
\r
14 Received: from olra.theworths.org ([127.0.0.1])
\r
15 by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)
\r
16 with ESMTP id CmtshuSstImd for <notmuch@notmuchmail.org>;
\r
17 Sat, 3 May 2014 11:57:33 -0700 (PDT)
\r
18 Received: from mail2.qmul.ac.uk (mail2.qmul.ac.uk [138.37.6.6])
\r
19 (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
\r
20 (No client certificate requested)
\r
21 by olra.theworths.org (Postfix) with ESMTPS id D2935431E64
\r
22 for <notmuch@notmuchmail.org>; Sat, 3 May 2014 11:57:32 -0700 (PDT)
\r
23 Received: from smtp.qmul.ac.uk ([138.37.6.40])
\r
24 by mail2.qmul.ac.uk with esmtp (Exim 4.71)
\r
25 (envelope-from <m.walters@qmul.ac.uk>)
\r
26 id 1Wgf7d-0001f6-Ik; Sat, 03 May 2014 19:57:27 +0100
\r
27 Received: from 5751dfa2.skybroadband.com ([87.81.223.162] helo=localhost)
\r
28 by smtp.qmul.ac.uk with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.71)
\r
29 (envelope-from <m.walters@qmul.ac.uk>)
\r
30 id 1Wgf7d-0007R8-8H; Sat, 03 May 2014 19:57:17 +0100
\r
31 From: Mark Walters <markwalters1009@gmail.com>
\r
32 To: David Mazieres expires 2014-08-01 PDT
\r
33 <mazieres-kdhm6yewp4dq87x4tf5ix7eyxw@temporary-address.scs.stanford.edu>,
\r
34 Jani Nikula <jani@nikula.org>
\r
35 Subject: Re: folder and path completely broken in HEAD?
\r
36 In-Reply-To: <87iopmonzn.fsf@ta.scs.stanford.edu>
\r
37 References: <87oazfo3w2.fsf@ta.scs.stanford.edu> <87zjiz8hft.fsf@qmul.ac.uk>
\r
38 <87iopmonzn.fsf@ta.scs.stanford.edu>
\r
39 User-Agent: Notmuch/0.15.2+615~g78e3a93 (http://notmuchmail.org) Emacs/23.4.1
\r
40 (x86_64-pc-linux-gnu)
\r
41 Date: Sat, 03 May 2014 19:57:15 +0100
\r
42 Message-ID: <87ppju4rn8.fsf@qmul.ac.uk>
\r
44 Content-Type: text/plain; charset=us-ascii
\r
45 X-Sender-Host-Address: 87.81.223.162
\r
46 X-QM-Geographic: According to ripencc,
\r
47 this message was delivered by a machine in Britain (UK) (GB).
\r
48 X-QM-SPAM-Info: Sender has good ham record. :)
\r
49 X-QM-Body-MD5: 2b402357401b55cb326276c6e6662c14 (of first 20000 bytes)
\r
50 X-SpamAssassin-Score: -0.1
\r
51 X-SpamAssassin-SpamBar: /
\r
52 X-SpamAssassin-Report: The QM spam filters have analysed this message to
\r
54 spam. We require at least 5.0 points to mark a message as spam.
\r
55 This message scored -0.1 points.
\r
56 Summary of the scoring:
\r
57 * 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail
\r
58 provider * (markwalters1009[at]gmail.com)
\r
59 * -0.1 AWL AWL: From: address is in the auto white-list
\r
60 X-QM-Scan-Virus: ClamAV says the message is clean
\r
61 Cc: notmuch@notmuchmail.org
\r
62 X-BeenThere: notmuch@notmuchmail.org
\r
63 X-Mailman-Version: 2.1.13
\r
65 List-Id: "Use and development of the notmuch mail system."
\r
66 <notmuch.notmuchmail.org>
\r
67 List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,
\r
68 <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>
\r
69 List-Archive: <http://notmuchmail.org/pipermail/notmuch>
\r
70 List-Post: <mailto:notmuch@notmuchmail.org>
\r
71 List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>
\r
72 List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,
\r
73 <mailto:notmuch-request@notmuchmail.org?subject=subscribe>
\r
74 X-List-Received-Date: Sat, 03 May 2014 18:57:37 -0000
\r
79 On Sat, 03 May 2014, dm-list-email-notmuch@scs.stanford.edu wrote:
\r
80 > Mark Walters <markwalters1009@gmail.com> writes:
\r
82 >>> All the way back. Now you are saying there will be no convenient way to
\r
83 >>> match just the "mail.class" part without the year? How very
\r
84 >>> distressing. Ugh.
\r
88 >> I am not quite sure what you are meaning by hierarchically group
\r
89 >> messages. Searching for path:dir/foo/bar/** should give all messages in
\r
90 >> all directories beneath dir/foo/bar.
\r
92 > The problem is that the maildir++ spec disallows such pathnames. If I
\r
93 > need compatibility with maildir++ (for instance for an imap server), at
\r
94 > least on a per-year basis, then my maildirs have to have names like:
\r
103 > So if I want a way to aggregate all my foo mail in a single search,
\r
104 > right now I just ask for folder:foo. Will there be any equivalent in
\r
107 I agree with Jani that for 0.18 this won't be possible. However, there
\r
108 is probably no urgent reason to upgrade (given you know it will cause
\r
109 you some problems) so the question is can we add some functionality to
\r
110 cover this use case. Given the way we do the folder matching I think it
\r
111 unlikely we would want to add globbing/wildcards to the start of a path
\r
114 However, we might be able to support maildir++ as its own prefix. If you
\r
115 could so searches of the form maildir++:.foo.bar.** which would match
\r
116 the maildir .foo.bar and all submaildirs++ (eg .foo.bar.a.b etc) would
\r
117 that be sufficient?
\r
119 This wouldn't deal with 2013/.foo.bar but would allow .foo.bar.2013
\r
121 Would this be enough help to make it worth considering?
\r
127 (*) if we get a custom parser then it may all be manageable.
\r
projects / notmuch-archives.git / blob