1 Return-Path: <jrollins@finestructure.net>
\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 5B271431FBD
\r
6 for <notmuch@notmuchmail.org>; Fri, 5 Feb 2010 09:49:33 -0800 (PST)
\r
7 X-Virus-Scanned: Debian amavisd-new at olra.theworths.org
\r
11 X-Spam-Status: No, score=-3.839 tagged_above=-999 required=5 tests=[AWL=0.160,
\r
12 BAYES_50=0.001, RCVD_IN_DNSWL_MED=-4] 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 ZlJKg3SufGV6 for <notmuch@notmuchmail.org>;
\r
16 Fri, 5 Feb 2010 09:49:32 -0800 (PST)
\r
17 Received: from serrano.cc.columbia.edu (serrano.cc.columbia.edu [128.59.29.6])
\r
18 by olra.theworths.org (Postfix) with ESMTP id AAECE431FAE
\r
19 for <notmuch@notmuchmail.org>; Fri, 5 Feb 2010 09:49:32 -0800 (PST)
\r
20 Received: from servo.finestructure.net (geco.phys.columbia.edu
\r
22 (user=jgr2110 author=jrollins@finestructure.net mech=PLAIN bits=0)
\r
23 by serrano.cc.columbia.edu (8.14.3/8.14.3) with ESMTP id o15HnVb8000683
\r
24 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT);
\r
25 Fri, 5 Feb 2010 12:49:32 -0500 (EST)
\r
26 Received: from jrollins by servo.finestructure.net with local (Exim 4.71)
\r
27 (envelope-from <jrollins@finestructure.net>)
\r
28 id 1NdSJ9-0007Ov-M2; Fri, 05 Feb 2010 12:49:31 -0500
\r
29 From: Jameson Graef Rollins <jrollins@finestructure.net>
\r
30 To: Marten Veldthuis <marten@veldthuis.com>, Notmuch Mail
\r
31 <notmuch@notmuchmail.org>
\r
32 In-Reply-To: <87zl3nr3vc.fsf@marten.rgoc.rug.nl>
\r
33 References: <878wb7wsnt.fsf@servo.finestructure.net>
\r
34 <87zl3nr3vc.fsf@marten.rgoc.rug.nl>
\r
35 Date: Fri, 05 Feb 2010 12:49:21 -0500
\r
36 Message-ID: <871vgzwp26.fsf@servo.finestructure.net>
\r
38 Content-Type: multipart/signed; boundary="=-=-=";
\r
39 micalg=pgp-sha256; protocol="application/pgp-signature"
\r
40 X-No-Spam-Score: Local
\r
41 X-Scanned-By: MIMEDefang 2.68 on 128.59.29.6
\r
42 Subject: Re: [notmuch] loss of duplicate messages
\r
43 X-BeenThere: notmuch@notmuchmail.org
\r
44 X-Mailman-Version: 2.1.13
\r
46 List-Id: "Use and development of the notmuch mail system."
\r
47 <notmuch.notmuchmail.org>
\r
48 List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,
\r
49 <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>
\r
50 List-Archive: <http://notmuchmail.org/pipermail/notmuch>
\r
51 List-Post: <mailto:notmuch@notmuchmail.org>
\r
52 List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>
\r
53 List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,
\r
54 <mailto:notmuch-request@notmuchmail.org?subject=subscribe>
\r
55 X-List-Received-Date: Fri, 05 Feb 2010 17:49:33 -0000
\r
58 Content-Transfer-Encoding: quoted-printable
\r
60 On Fri, 05 Feb 2010 18:25:59 +0100, Marten Veldthuis <marten@veldthuis.com>=
\r
62 > This is indeed the correct behaviour of notmuch. There has been some
\r
63 > discussion on it in the past, I believe with proposals to track both
\r
64 > messages and show only one; but I don't think I've seen proponents of
\r
65 > showing both duplicate messages.
\r
67 > Personally I'd find it rather annoying if I'd see messages twice. But I
\r
68 > do see the value in being sure that your mail gets delivered through the
\r
69 > list. I believe the solution I've seen discussed was for notmuch to
\r
70 > somehow determine which of the duplicates holds the most information
\r
71 > (which would be the one through the list, not the one directly to you).
\r
73 Hey, Marten. Thanks for the reply.
\r
75 The problem I have with only returning one of the redundant messages is
\r
76 that I don't think anyone could ever really convince me that notmuch has
\r
77 the ability to decide which of the redundant messages is the *right* one
\r
78 to return. I think notmuch is currently just returning the first one it
\r
79 indexes, but why is that better than returning the one most recently
\r
82 A policy of only returning one is going to be problematic for folks who
\r
83 want or expect to see the other. And in fact think I want to see both.
\r
84 I have both, and I've asked notmuch to index both, so why shouldn't it
\r
85 return both in a search?
\r
90 Content-Type: application/pgp-signature
\r
92 -----BEGIN PGP SIGNATURE-----
\r
93 Version: GnuPG v1.4.10 (GNU/Linux)
\r
95 iQIcBAEBCAAGBQJLbFoiAAoJEO00zqvie6q8cNgP/jE2Saj7zDn8MbGSQmVryCfh
\r
96 J2kGCGmhYFTCEuzlt8QvbKFT27i4Z2Fre5Apz4M0NwcGimMqYyQ3W3YDMsqUCfqA
\r
97 4kHVZLjH+/Ee7t9Z5NGGqoRkt9nSWjCT7qeM2A4/vVgQrbkU4qN6y6MXCc+hX24o
\r
98 Uyx+WORNC06W9dnU8Pnhrz9gBKPaI3BCY5zhtdyqr77tuWaQazoAfspZ3wJRkJub
\r
99 O6eZYZdKFc+whsSOFfzCX9KeQ7+G1tYP2bjjL5DYhiJR7cYPXN8dfHOawY/2zyzz
\r
100 GF32eT229v+bB+4auMEXI7nIO9eJ6us6KglNXQghwUi9JUX3aFXxEyqwOVankCHU
\r
101 9MyZ+npLh6o3IaLBTi4fL73JPMYO+FxbJoHq4u42M0yk/2isCT/ejOKZ1b8+E6S/
\r
102 o2CIatckE1NDzFM4rWnrFmfBIp3GbSbOEjo8t690D/glGq2OdRcyA0j6W8h+gmB5
\r
103 jw0I+AB9t+rX/x6Th1QOOHyQSWuw0jePrysaon2pS4fjW0Q7SbqIXHxVSmq+mi6F
\r
104 GX89alCQxmpL8RE9NGjA5T+FKr+7Nl9ZTJ9xwH74b5utR78tSPpENPhLiwnaTb+Q
\r
105 OwViyKy+DfnZvOxGg2w0ng7RHJGCEsgyKI5TX5PumapImAxqhKZ6dDdeVQdHPCHk
\r
106 nUpKptAx+76gy3cQMNds
\r
108 -----END PGP SIGNATURE-----
\r