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 92464431FBD;
\r
6 Fri, 4 Dec 2009 16:32:07 -0800 (PST)
\r
7 X-Virus-Scanned: Debian amavisd-new at olra.theworths.org
\r
8 Received: from olra.theworths.org ([127.0.0.1])
\r
9 by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)
\r
10 with ESMTP id vjp0uPWtAv0s; Fri, 4 Dec 2009 16:32:06 -0800 (PST)
\r
11 Received: from yoom.home.cworth.org (localhost [127.0.0.1])
\r
12 by olra.theworths.org (Postfix) with ESMTP id CA4C5431FAE;
\r
13 Fri, 4 Dec 2009 16:32:06 -0800 (PST)
\r
14 Received: by yoom.home.cworth.org (Postfix, from userid 1000)
\r
15 id 7FAB02542FB; Fri, 4 Dec 2009 16:32:06 -0800 (PST)
\r
16 From: Carl Worth <cworth@cworth.org>
\r
17 To: Michael Alan Dorman <mdorman@ironicdesign.com>, notmuch@notmuchmail.org
\r
18 In-Reply-To: <20091204140946.644243f0@vimes.local>
\r
19 References: <1259267025-28733-1-git-send-email-dottedmag@dottedmag.net>
\r
20 <1259788526-14205-1-git-send-email-dottedmag@dottedmag.net>
\r
21 <87zl5zfty5.fsf@yoom.home.cworth.org>
\r
22 <87k4x29732.wl%bremner@pivot.cs.unb.ca>
\r
23 <87bpiefwdq.fsf@yoom.home.cworth.org> <87aaxysjdj.fsf@vertex.dottedmag>
\r
24 <87aaxyfuz4.fsf@yoom.home.cworth.org>
\r
25 <20091204140946.644243f0@vimes.local>
\r
26 Date: Fri, 04 Dec 2009 16:32:06 -0800
\r
27 Message-ID: <87iqcmdzw9.fsf@yoom.home.cworth.org>
\r
29 Content-Type: multipart/signed; boundary="=-=-=";
\r
30 micalg=pgp-sha1; protocol="application/pgp-signature"
\r
31 Subject: Re: [notmuch] [PATCH (rebased)] Handle message renames in mail spool
\r
32 X-BeenThere: notmuch@notmuchmail.org
\r
33 X-Mailman-Version: 2.1.12
\r
35 List-Id: "Use and development of the notmuch mail system."
\r
36 <notmuch.notmuchmail.org>
\r
37 List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,
\r
38 <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>
\r
39 List-Archive: <http://notmuchmail.org/pipermail/notmuch>
\r
40 List-Post: <mailto:notmuch@notmuchmail.org>
\r
41 List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>
\r
42 List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,
\r
43 <mailto:notmuch-request@notmuchmail.org?subject=subscribe>
\r
44 X-List-Received-Date: Sat, 05 Dec 2009 00:32:07 -0000
\r
47 Content-Transfer-Encoding: quoted-printable
\r
49 On Fri, 4 Dec 2009 14:09:46 -0500, Michael Alan Dorman <mdorman@ironicdesig=
\r
51 > Now, if you have an MTA that does duplicate suppression based on
\r
52 > message-id, you probably won't see the copy of a message that went to
\r
53 > the list if you're cc:'d on it because the direct copy (sans list-id
\r
54 > header) is likely to arrive first.
\r
56 > I would argue that that's a feature not a bug---the sender, at least,
\r
57 > hopes you will give it closer scrutiny because you were CC:'d. They're
\r
58 > trying to bring it to your attention.
\r
60 Sure, giving it closer scrutiny is good. But if I expect a search like:
\r
64 to match all of my mail that came through the mailing list, but it
\r
65 actually *misses* mail where the sender wanted me to give extra
\r
66 scrutiny, then that's a big failure.
\r
68 > Besides, in notmuch, what's the difference going to be? It'll still be
\r
69 > threaded the same, etc., but you'd be able to tell that this one came
\r
70 > to you rather than through the list, no?
\r
72 The difference is whether the message is found in a search, (see above).
\r
74 > (I'm waiting for Debian packages, lazy bastard that I am, so I'm
\r
77 Yeah, I'll get to that (real soon now, I promise.)
\r
79 > On the linux-kernel list, l-k often isn't in the to: field---or does
\r
80 > notmuch also index the cc: as to:? If it does, this could work; if
\r
83 Yes. In notmuch, all recipient fields, (even Bcc: if a mail happens to
\r
84 hit your mail store with that intact), all get indexed to a single "to"
\r
85 prefix. My rationale is that when reading a message it's often very
\r
86 useful to see whether I was addresses specifically or just CC'ed. But
\r
87 when _searching_ for a message, it's too fragile to have to guess
\r
88 whether the recipient was on the To: or CC: header (and too painful to
\r
89 always type (to:me@example.com or cc:me@example.com).
\r
94 Content-Type: application/pgp-signature
\r
96 -----BEGIN PGP SIGNATURE-----
\r
97 Version: GnuPG v1.4.10 (GNU/Linux)
\r
99 iD8DBQFLGaoG6JDdNq8qSWgRAqeJAJ9pfif263SSFE/vS1QNMIc6Hy4mwgCffJQp
\r
100 zuMPKlRIaZC79djF7o9z2/8=
\r
102 -----END PGP SIGNATURE-----
\r