1 Return-Path: <tomi.ollila@nixu.com>
\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 5CD28429E26
\r
6 for <notmuch@notmuchmail.org>; Tue, 6 Dec 2011 14:03:37 -0800 (PST)
\r
7 X-Virus-Scanned: Debian amavisd-new at olra.theworths.org
\r
11 X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[none]
\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 G6SoKmVC2r8f for <notmuch@notmuchmail.org>;
\r
16 Tue, 6 Dec 2011 14:03:32 -0800 (PST)
\r
17 Received: from mail-gw3.nixu.fi (mail-gw3.nixu.fi [193.209.237.7])
\r
18 (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
\r
19 (No client certificate requested)
\r
20 by olra.theworths.org (Postfix) with ESMTPS id 8F3D2429E21
\r
21 for <notmuch@notmuchmail.org>; Tue, 6 Dec 2011 14:03:32 -0800 (PST)
\r
22 Received: from pps.filterd (mail-gw3 [127.0.0.1])
\r
23 by mail-gw3.nixu.fi (8.14.4/8.14.4) with SMTP id pB6M3NKS019422;
\r
24 Wed, 7 Dec 2011 00:03:23 +0200
\r
25 Received: from taco2.nixu.fi (taco2.nixu.fi [194.197.118.31])
\r
26 by mail-gw3.nixu.fi with ESMTP id 114cs0qp39-1
\r
27 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT);
\r
28 Wed, 07 Dec 2011 00:03:22 +0200
\r
29 Received: from taco2.nixu.fi (taco2.nixu.fi [194.197.118.31])
\r
30 by taco2.nixu.fi (8.14.3/8.14.3/Debian-5+lenny1) with ESMTP id
\r
31 pB6M3JHV020023; Wed, 7 Dec 2011 00:03:20 +0200
\r
32 From: Tomi Ollila <tomi.ollila@iki.fi>
\r
33 To: Bart Bunting <bart@ursys.com.au>,
\r
34 Jameson Graef Rollins <jrollins@finestructure.net>, notmuch@notmuchmail.org
\r
35 Subject: Re: ANNOUNCE: nottoomuch-addresses.pl
\r
36 In-Reply-To: <m2k46a3d6a.fsf@ursys.com.au>
\r
37 References: <m2d3c8e22v.fsf@guru.guru-group.fi> <m2vcq0qgs6.fsf@ursys.com.au>
\r
38 <yf6wraf5sq2.fsf@taco2.nixu.fi> <yf68vmr5j9n.fsf@taco2.nixu.fi>
\r
39 <m2pqg32pic.fsf@ursys.com.au> <yf662hv5h8o.fsf@taco2.nixu.fi>
\r
40 <87wrabmb43.fsf@servo.finestructure.net>
\r
41 <m2k46a3d6a.fsf@ursys.com.au>
\r
42 User-Agent: Notmuch/0.10+55~gde3d46e (http://notmuchmail.org) Emacs/23.3.1
\r
44 X-Face: HhBM'cA~<r"^Xv\KRN0P{vn'Y"Kd;zg_y3S[4)KSN~s?O\"QPoL
\r
45 $[Xv_BD:i/F$WiEWax}R(MPS`^UaptOGD`*/=@\1lKoVa9tnrg0TW?"r7aRtgk[F
\r
46 !)g;OY^,BjTbr)Np:%c_o'jj,Z
\r
47 Date: Wed, 07 Dec 2011 00:03:19 +0200
\r
48 Message-ID: <yf639cx5peg.fsf@taco2.nixu.fi>
\r
50 Content-Type: text/plain; charset=us-ascii
\r
51 X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.5.7110,
\r
52 1.0.211, 0.0.0000 definitions=2011-12-06_04:2011-12-06, 2011-12-06,
\r
53 1970-01-01 signatures=0
\r
54 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0
\r
55 ipscore=0 suspectscore=0
\r
56 phishscore=0 bulkscore=0 adultscore=0 classifier=spam adjust=0
\r
58 scancount=1 engine=6.0.2-1012030000 definitions=main-1112060242
\r
59 X-BeenThere: notmuch@notmuchmail.org
\r
60 X-Mailman-Version: 2.1.13
\r
62 List-Id: "Use and development of the notmuch mail system."
\r
63 <notmuch.notmuchmail.org>
\r
64 List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,
\r
65 <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>
\r
66 List-Archive: <http://notmuchmail.org/pipermail/notmuch>
\r
67 List-Post: <mailto:notmuch@notmuchmail.org>
\r
68 List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>
\r
69 List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,
\r
70 <mailto:notmuch-request@notmuchmail.org?subject=subscribe>
\r
71 X-List-Received-Date: Tue, 06 Dec 2011 22:03:37 -0000
\r
73 On Tue, 06 Dec 2011 08:45:49 +1100, Bart Bunting <bart@ursys.com.au> wrote:
\r
76 > I agree with Jamie on this one.
\r
78 > The case sensitivity appears to get in the way of searching. I also
\r
79 > think that enabling the regular expression searching is a good idea.
\r
81 > All in all though this is great.
\r
83 I did version 1.2 of nottoomuch-addresses.sh which does case insensitive
\r
84 searches. Note the renaming to .sh -- it is now shell script wrapper
\r
85 which runs 'exec grep -aiF "$*" <addresses-file> -- grep is locale-aware
\r
86 which makes case insensitivity work outside of ASCII range. The perl code
\r
87 to create/update addresses file is exactly the same as in version 1.1
\r
89 So, the current version (1.2) is available at
\r
91 http://www.iki.fi/too/nottoomuch/nottoomuch-addresses.sh
\r
93 sha1sum is 03aa8bcf4e32d47e453fc081376843ef03a427ad and doc page is at
\r
95 http://www.iki.fi/too/nottoomuch/nottoomuch-addresses/
\r
97 > The only other idea I have, which is only half formed, is that it would
\r
98 > be nice to prioritize emails that are more important than others.
\r
100 > I'm not sure exactly how this would work but something like:
\r
101 > - Addresses I have actualy sent email to rather than jjust received from
\r
102 > get a high priority in the result.
\r
103 > - Addresses that have sent me email directly rather than just to a list
\r
104 > get next priority.
\r
105 > - All other emails after that.
\r
107 > Also some sort of weighting within the groups to do with frequency of
\r
108 > emails sent or something.
\r
110 > Does that make sense? Would it be hard to implement?
\r
112 Neat idea. To implement the feature into program is not too hard.
\r
113 Somehow determine weight for each email address, store that into
\r
114 hash (key address, value weight).
\r
115 Then, when writing addresses file, sort first by weight and then
\r
116 ascii order. The hash is also stored to disk (using tie()) and used
\r
117 when address file updated.
\r
119 Now, how to determine good (generic) rules for weights (and maybe
\r
120 some user-defined rules as well) is the question.
\r
projects / notmuch-archives.git / blob