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 3F746431FAE
\r
6 for <notmuch@notmuchmail.org>; Fri, 21 Nov 2014 07:10:35 -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 cULzEf8tPVJo for <notmuch@notmuchmail.org>;
\r
17 Fri, 21 Nov 2014 07:10:31 -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 D97F9431FB6
\r
22 for <notmuch@notmuchmail.org>; Fri, 21 Nov 2014 07:10:30 -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 1Xrpqm-0005N7-5G; Fri, 21 Nov 2014 15:10:24 +0000
\r
27 Received: from sc-4173-rec-r1.memphis.edu ([141.225.189.252] 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 1XrpqP-0006C5-Or; Fri, 21 Nov 2014 15:10:19 +0000
\r
31 From: Mark Walters <markwalters1009@gmail.com>
\r
32 To: Olivier Berger <olivier.berger@telecom-sudparis.eu>,
\r
33 David Bremner <david@tethera.net>
\r
34 Subject: Re: tag:deleted messages immediately deleted ?
\r
35 In-Reply-To: <87d28gd703.fsf@inf-11879.int-evry.fr>
\r
36 References: <877fyseuq8.fsf@inf-11879.int-evry.fr>
\r
37 <87d28ku7rt.fsf@maritornes.cs.unb.ca>
\r
38 <871tp0ek8b.fsf@inf-11879.int-evry.fr>
\r
39 <87lhn8fmq9.fsf@maritornes.cs.unb.ca>
\r
40 <877fypre49.fsf@inf-11879.int-evry.fr>
\r
41 <87r3wx9eaq.fsf@maritornes.cs.unb.ca>
\r
42 <87d28gd703.fsf@inf-11879.int-evry.fr>
\r
43 User-Agent: Notmuch/0.18.1+86~gef5e66a (http://notmuchmail.org) Emacs/23.4.1
\r
44 (x86_64-pc-linux-gnu)
\r
45 Date: Fri, 21 Nov 2014 15:08:59 +0000
\r
46 Message-ID: <87zjbkwpys.fsf@qmul.ac.uk>
\r
48 Content-Type: text/plain; charset=us-ascii
\r
49 X-Sender-Host-Address: 141.225.189.252
\r
50 X-QM-Geographic: According to ripencc,
\r
51 this message was delivered by a machine in Britain (UK) (GB).
\r
52 X-QM-SPAM-Info: Sender has good ham record. :)
\r
53 X-QM-Body-MD5: 1c2cbafe1c8c90cf7817093762570a94 (of first 20000 bytes)
\r
54 X-SpamAssassin-Score: -0.0
\r
55 X-SpamAssassin-SpamBar: /
\r
56 X-SpamAssassin-Report: The QM spam filters have analysed this message to
\r
58 spam. We require at least 5.0 points to mark a message as spam.
\r
59 This message scored -0.0 points.
\r
60 Summary of the scoring:
\r
61 * 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail
\r
62 provider * (markwalters1009[at]gmail.com)
\r
63 * -0.0 T_RP_MATCHES_RCVD Envelope sender domain matches handover relay
\r
65 X-QM-Scan-Virus: ClamAV says the message is clean
\r
66 Cc: notmuch@notmuchmail.org
\r
67 X-BeenThere: notmuch@notmuchmail.org
\r
68 X-Mailman-Version: 2.1.13
\r
70 List-Id: "Use and development of the notmuch mail system."
\r
71 <notmuch.notmuchmail.org>
\r
72 List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,
\r
73 <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>
\r
74 List-Archive: <http://notmuchmail.org/pipermail/notmuch>
\r
75 List-Post: <mailto:notmuch@notmuchmail.org>
\r
76 List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>
\r
77 List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,
\r
78 <mailto:notmuch-request@notmuchmail.org?subject=subscribe>
\r
79 X-List-Received-Date: Fri, 21 Nov 2014 15:10:35 -0000
\r
81 On Fri, 21 Nov 2014, Olivier Berger <olivier.berger@telecom-sudparis.eu> wrote:
\r
82 > David Bremner <david@tethera.net> writes:
\r
84 >> Olivier Berger <olivier.berger@telecom-sudparis.eu> writes:
\r
87 >>> So, I've tried and removed the spam tag from the exclude_tags, and
\r
88 >>> suddenly, the search in emacs responds with the 981... which means that
\r
89 >>> most of the deleted ones had the spam tag too.
\r
92 >>> So it means that if one explicitely requests an excluded tag, other
\r
93 >>> exclude tags still apply. Not sure this is the desirable option : maybe
\r
94 >>> if one exclusion is waved, then others should too ?
\r
96 >>> What do you think ?
\r
98 >> I'm not sure. What you suggest sounds sensible enough. On the other hand
\r
99 >> the way it behaves now is precisely as documented; I'm not sure whether
\r
100 >> this is because of a design choice or ease of implementation. Maybe Mark
\r
101 >> can comment further on that. I guess there are even people who
\r
102 >> like/rely on the current functionality, since there always are ;).
\r
104 This was definitely a design choice (I think probably by Austin/jrollins) and I
\r
105 think it makes sense: why would you want to include one include spam
\r
106 messages when you are searching for deleted messages?
\r
108 A change would break my setup - not in itself a problem as I setup this
\r
109 way to make sure I exercised the exclude code. I tag all my notmuch
\r
110 mailing list mail tag:notmuch and have that as an excluded tag. Then
\r
111 mailing list results do not clutter up results when I am doing personal
\r
116 > In any case, there has been a change in the way this worked.
\r
118 I don't think anyone has touched this code for over two years: git blame
\r
119 seems to suggest March 2012.
\r
121 > For the moment, I'm using the following saved search :
\r
122 > (tag:deleted or tag:spam) and tag:deleted
\r
123 > which will display the deleted mails.
\r
125 I do think it would be nice to have a clear way of turning excludes off
\r
126 in the emacs frontend. Without a query parser it's not clear what the
\r
127 best way to do it is: I suggested a hack which allowed --exclude=false
\r
128 to be passed as part of the search. We could add a toggle to rerun a
\r
129 search with exclude=false but that doesn't help much for saved searches
\r
130 or manually entered searches.
\r