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 A1AC9429E54
\r
6 for <notmuch@notmuchmail.org>; Sat, 21 Jan 2012 16:38:08 -0800 (PST)
\r
7 X-Virus-Scanned: Debian amavisd-new at olra.theworths.org
\r
11 X-Spam-Status: No, score=-1.098 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_MED=-2.3] 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 CCMGBHe+DWgv for <notmuch@notmuchmail.org>;
\r
17 Sat, 21 Jan 2012 16:38:08 -0800 (PST)
\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 EC316429E40
\r
22 for <notmuch@notmuchmail.org>; Sat, 21 Jan 2012 16:38:07 -0800 (PST)
\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 1RolRZ-0003tn-Df; Sun, 22 Jan 2012 00:38:03 +0000
\r
27 Received: from 94-192-233-223.zone6.bethere.co.uk ([94.192.233.223]
\r
29 by smtp.qmul.ac.uk with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.69)
\r
30 (envelope-from <m.walters@qmul.ac.uk>)
\r
31 id 1RolRZ-0004V0-4z; Sun, 22 Jan 2012 00:38:01 +0000
\r
32 From: Mark Walters <markwalters1009@gmail.com>
\r
33 To: Austin Clements <amdragon@MIT.EDU>
\r
34 Subject: Re: [PATCH] Automatically exclude tags in notmuch-show
\r
35 In-Reply-To: <20120120171801.GA16740@mit.edu>
\r
36 References: <874nvric7c.fsf@qmul.ac.uk>
\r
37 <1327010583-23954-1-git-send-email-markwalters1009@gmail.com>
\r
38 <20120119225910.GT16740@mit.edu> <871uqvgrnm.fsf@qmul.ac.uk>
\r
39 <20120120171801.GA16740@mit.edu>
\r
40 User-Agent: Notmuch/0.11+77~gad6d0d5 (http://notmuchmail.org) Emacs/23.2.1
\r
42 Date: Sun, 22 Jan 2012 00:38:56 +0000
\r
43 Message-ID: <87sjj8efkv.fsf@qmul.ac.uk>
\r
45 Content-Type: text/plain; charset=us-ascii
\r
46 X-Sender-Host-Address: 94.192.233.223
\r
47 X-QM-SPAM-Info: Sender has good ham record. :)
\r
48 X-QM-Body-MD5: 5c1f9aa1bccd3f1fa92cbb62d07ac311 (of first 20000 bytes)
\r
49 X-SpamAssassin-Score: -1.8
\r
50 X-SpamAssassin-SpamBar: -
\r
51 X-SpamAssassin-Report: The QM spam filters have analysed this message to
\r
53 spam. We require at least 5.0 points to mark a message as spam.
\r
54 This message scored -1.8 points.
\r
55 Summary of the scoring:
\r
56 * -2.3 RCVD_IN_DNSWL_MED RBL: Sender listed at http://www.dnswl.org/,
\r
58 * [138.37.6.40 listed in list.dnswl.org]
\r
59 * 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail
\r
60 provider * (markwalters1009[at]gmail.com)
\r
61 * -0.0 T_RP_MATCHES_RCVD Envelope sender domain matches handover relay
\r
63 * 0.5 AWL AWL: From: address is in the auto white-list
\r
64 X-QM-Scan-Virus: ClamAV says the message is clean
\r
65 Cc: notmuch@notmuchmail.org
\r
66 X-BeenThere: notmuch@notmuchmail.org
\r
67 X-Mailman-Version: 2.1.13
\r
69 List-Id: "Use and development of the notmuch mail system."
\r
70 <notmuch.notmuchmail.org>
\r
71 List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,
\r
72 <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>
\r
73 List-Archive: <http://notmuchmail.org/pipermail/notmuch>
\r
74 List-Post: <mailto:notmuch@notmuchmail.org>
\r
75 List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>
\r
76 List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,
\r
77 <mailto:notmuch-request@notmuchmail.org?subject=subscribe>
\r
78 X-List-Received-Date: Sun, 22 Jan 2012 00:38:08 -0000
\r
81 On Fri, 20 Jan 2012 12:18:01 -0500, Austin Clements <amdragon@MIT.EDU> wrote:
\r
85 > Well, here's one idea. Instead of doing a single thread query in
\r
86 > show, do a thread query without the exclusions and then a message
\r
87 > query with the exclusions. Output all of the messages from the first
\r
88 > query, but use the results of the second query to determine which
\r
89 > messages are "matched". The same could be accomplished in the library
\r
90 > somewhat more efficiently, but it's not obvious to me what the API
\r
93 I have been thinking about this and one question is what should the sort
\r
94 order be? If I understand it correctly notmuch sorts the threads
\r
95 by the oldest/newest matching message, so the "correct" behaviour if no
\r
96 message matches is unclear. Perhaps all threads with a matching
\r
97 non-excluded message sorted by the matching-non-excluded message
\r
98 followed by all threads that match only on excluded messages with sort
\r
99 based on the matching excluded message?
\r