1 Return-Path: <dkg@fifthhorseman.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 BD1B1431FAE
\r
6 for <notmuch@notmuchmail.org>; Thu, 8 Mar 2012 13:40:01 -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 QBW3uQQDZqcO for <notmuch@notmuchmail.org>;
\r
16 Thu, 8 Mar 2012 13:40:01 -0800 (PST)
\r
17 Received: from che.mayfirst.org (che.mayfirst.org [209.234.253.108])
\r
18 by olra.theworths.org (Postfix) with ESMTP id 306E1431FB6
\r
19 for <notmuch@notmuchmail.org>; Thu, 8 Mar 2012 13:40:01 -0800 (PST)
\r
20 Received: from [192.168.13.75] (lair.fifthhorseman.net [108.58.6.98])
\r
21 by che.mayfirst.org (Postfix) with ESMTPSA id A083DF970
\r
22 for <notmuch@notmuchmail.org>; Thu, 8 Mar 2012 16:39:58 -0500 (EST)
\r
23 Message-ID: <4F592730.2040908@fifthhorseman.net>
\r
24 Date: Thu, 08 Mar 2012 16:40:00 -0500
\r
25 From: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
\r
26 User-Agent: Mozilla/5.0 (X11; Linux i686; rv:9.0) Gecko/20120125 Icedove/9.0.1
\r
28 To: notmuch <notmuch@notmuchmail.org>
\r
29 Subject: Re: Parsing regression with gmime-2.6?
\r
30 References: <87d38w2e7h.fsf@zancas.localnet>
\r
31 <1331058417-13776-1-git-send-email-amdragon@mit.edu>
\r
32 <87wr6xmlml.fsf@zancas.localnet>
\r
33 <87vcme3kf6.fsf@pip.fifthhorseman.net>
\r
34 <874ntybwxv.fsf@servo.finestructure.net>
\r
35 In-Reply-To: <874ntybwxv.fsf@servo.finestructure.net>
\r
36 Content-Type: text/plain; charset=UTF-8; format=flowed
\r
37 Content-Transfer-Encoding: 7bit
\r
38 X-BeenThere: notmuch@notmuchmail.org
\r
39 X-Mailman-Version: 2.1.13
\r
41 Reply-To: notmuch <notmuch@notmuchmail.org>
\r
42 List-Id: "Use and development of the notmuch mail system."
\r
43 <notmuch.notmuchmail.org>
\r
44 List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,
\r
45 <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>
\r
46 List-Archive: <http://notmuchmail.org/pipermail/notmuch>
\r
47 List-Post: <mailto:notmuch@notmuchmail.org>
\r
48 List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>
\r
49 List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,
\r
50 <mailto:notmuch-request@notmuchmail.org?subject=subscribe>
\r
51 X-List-Received-Date: Thu, 08 Mar 2012 21:40:01 -0000
\r
53 On 03/08/2012 04:32 PM, Jameson Graef Rollins wrote:
\r
55 > I actually agree with this position. mbox files are not proper email
\r
56 > messages, so if gmime does not explicitly support parsing them then we
\r
57 > really can't expect it to parse them.
\r
59 i think the point here is that gmime used to support parsing them and
\r
62 So if you've got a pre-existing notmuch index (built from when gmime
\r
63 *did* parse them) and you're now running notmuch linked against a gmime
\r
64 that *doesn't* parse them, then notmuch search will produce references
\r
65 to messages that notmuch show can't produce output for.
\r
67 While i appreciate wanting to be sure that we're working with
\r
68 well-formed files, I don't have a good answer for what the right thing
\r
69 to do is, if gmime upstream agrees with your assessment of the situation.
\r