1 Return-Path: <cworth@cworth.org>
\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 D174940D157
\r
6 for <notmuch@notmuchmail.org>; Fri, 29 Oct 2010 16:18:50 -0700 (PDT)
\r
7 X-Virus-Scanned: Debian amavisd-new at olra.theworths.org
\r
11 X-Spam-Status: No, score=-2.9 tagged_above=-999 required=5
\r
12 tests=[ALL_TRUSTED=-1, BAYES_00=-1.9] autolearn=ham
\r
13 Received: from olra.theworths.org ([127.0.0.1])
\r
14 by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)
\r
15 with ESMTP id kEyI9OK2oPSs; Fri, 29 Oct 2010 16:18:40 -0700 (PDT)
\r
16 Received: from yoom.home.cworth.org (localhost [127.0.0.1])
\r
17 by olra.theworths.org (Postfix) with ESMTP id 7F2B540D166;
\r
18 Fri, 29 Oct 2010 16:18:32 -0700 (PDT)
\r
19 Received: by yoom.home.cworth.org (Postfix, from userid 1000)
\r
20 id 23B72254007; Fri, 29 Oct 2010 16:18:32 -0700 (PDT)
\r
21 From: Carl Worth <cworth@cworth.org>
\r
22 To: Albin Stjerna <albin@eval.nu>, notmuch@notmuchmail.org
\r
23 Subject: Re: SpamAssassin or: why can't I search for =?utf-8?B?wrtbwqs/?=
\r
24 In-Reply-To: <87zkyvxkdd.fsf@nyx.luftslott.org>
\r
25 References: <87zkyvxkdd.fsf@nyx.luftslott.org>
\r
26 User-Agent: Notmuch/0.3.1 (http://notmuchmail.org) Emacs/23.2.1
\r
28 Date: Fri, 29 Oct 2010 16:18:31 -0700
\r
29 Message-ID: <871v78r3js.fsf@yoom.home.cworth.org>
\r
31 Content-Type: multipart/signed; boundary="=-=-=";
\r
32 micalg=pgp-sha1; protocol="application/pgp-signature"
\r
33 X-BeenThere: notmuch@notmuchmail.org
\r
34 X-Mailman-Version: 2.1.13
\r
36 List-Id: "Use and development of the notmuch mail system."
\r
37 <notmuch.notmuchmail.org>
\r
38 List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,
\r
39 <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>
\r
40 List-Archive: <http://notmuchmail.org/pipermail/notmuch>
\r
41 List-Post: <mailto:notmuch@notmuchmail.org>
\r
42 List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>
\r
43 List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,
\r
44 <mailto:notmuch-request@notmuchmail.org?subject=subscribe>
\r
45 X-List-Received-Date: Fri, 29 Oct 2010 23:18:51 -0000
\r
48 Content-Type: text/plain; charset=utf-8
\r
49 Content-Transfer-Encoding: quoted-printable
\r
51 On Wed, 16 Jun 2010 13:55:10 +0200, Albin Stjerna <albin@eval.nu> wrote:
\r
52 > I've been trying to get notmuch to apply the tag =C2=BBspam=C2=AB to thes=
\r
54 > but it seems I can neither make it search for upper-case letters nor
\r
55 > =C2=BB[=C2=AB/=C2=BB]=C2=AB. My current solution is to tag everything wit=
\r
56 h =C2=BBspam=C2=AB somewhere
\r
57 > in the subject header as spam, which leads to lots of false positives.
\r
61 I'm sorry that nobody answered this fairly simple question of yours
\r
64 What's happening here is that Xapian (the indexer used by notmuch) looks
\r
65 for "word characters" and "non-word characters" that separate
\r
66 words[*]. Then, the words are indexed (with numeric information
\r
67 indicating their position) and the separators are thrown away. So
\r
68 there's no way to search for separators such as =C2=BB[=C2=AB/=C2=BB]=C2=AB.
\r
70 As for case-sensitivity, Xapian does provide capabilities such that
\r
71 notmuch could offer optional case-sensitive searching. But that might
\r
72 require more storage space than notmuch is currently using. It would
\r
73 also require us to add some syntax to the search terms so that a user
\r
74 can request case-sensitive searches.
\r
76 Meanwhile, for a long-term fix for your problem, we plan to add the
\r
77 ability to allow you to use notmuch to search for a header such as
\r
78 "X-Spam-Flag: YES". This isn't currently possible, but when we implement
\r
79 that, it should be much more reliable than finding flagged spam by
\r
80 looking for words in the subject.
\r
82 > Also, and much less importantly, is there any way to have notmuch
\r
83 > harvest email addresses for BBDB?
\r
85 We haven't written code to do the "insinuate" into bbdb thing by
\r
86 default, but someone could do that. Early in my use of notmuch I wrote
\r
87 some scripts that ran notmuch commands, grepped out addresses, and
\r
88 stuffed them into bbdb. That was nice at first, but not usable in the
\r
89 long-term since the database didn't grow as new addresses appeared in
\r
92 More recently, we've added support to do tab-based completion of
\r
93 addresses based on automatic searching through your notmuch mail store,
\r
94 (rather than something external like bbdb). This is quite nice, but
\r
95 currently a bit of effort to setup. See the "how to get email address
\r
96 completion" instructions here:
\r
98 http://notmuchmail.org/emacstips/
\r
100 In the future, I'd like to get this address completion working by
\r
101 default without requiring the download of an additional tool, (like the
\r
102 current notmuch_addresses.py or addrlookup programs). Having more direct
\r
103 support for address completion within the notmuch database itself will
\r
104 make it faster as well, (the current tools are grubbing through actual
\r
105 mail files to find complete addresses).
\r
109 [*] I'm sure I'm using the wrong terminology for Xapian, and I might
\r
110 have some details wrong, but the basic idea is hopefully correct.
\r
113 carl.d.worth@intel.com
\r
116 Content-Type: application/pgp-signature
\r
118 -----BEGIN PGP SIGNATURE-----
\r
119 Version: GnuPG v1.4.10 (GNU/Linux)
\r
121 iD8DBQFMy1ZI6JDdNq8qSWgRAhV7AJsHpP2/t8g1Y0mQWg83y/zenZmRjACfZ3Oa
\r
122 V9quQ+a/luOMAsbGGkyRKYc=
\r
124 -----END PGP SIGNATURE-----
\r
projects / notmuch-archives.git / blob