Re: Parsing regression with gmime-2.6?

diff --git a/3d/8e51271f1527cc13583065de40d8691a785b3a b/3d/8e51271f1527cc13583065de40d8691a785b3a
new file mode 100644 (file)
index 0000000..075a9c2
--- /dev/null
+++ b/3d/8e51271f1527cc13583065de40d8691a785b3a
@@ -0,0 +1,73 @@
+Return-Path: <dkg@fifthhorseman.net>\r
+X-Original-To: notmuch@notmuchmail.org\r
+Delivered-To: notmuch@notmuchmail.org\r
+Received: from localhost (localhost [127.0.0.1])\r
+       by olra.theworths.org (Postfix) with ESMTP id BD1B1431FAE\r
+       for <notmuch@notmuchmail.org>; Thu,  8 Mar 2012 13:40:01 -0800 (PST)\r
+X-Virus-Scanned: Debian amavisd-new at olra.theworths.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: 0\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[none]\r
+       autolearn=disabled\r
+Received: from olra.theworths.org ([127.0.0.1])\r
+       by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)\r
+       with ESMTP id QBW3uQQDZqcO for <notmuch@notmuchmail.org>;\r
+       Thu,  8 Mar 2012 13:40:01 -0800 (PST)\r
+Received: from che.mayfirst.org (che.mayfirst.org [209.234.253.108])\r
+       by olra.theworths.org (Postfix) with ESMTP id 306E1431FB6\r
+       for <notmuch@notmuchmail.org>; Thu,  8 Mar 2012 13:40:01 -0800 (PST)\r
+Received: from [192.168.13.75] (lair.fifthhorseman.net [108.58.6.98])\r
+       by che.mayfirst.org (Postfix) with ESMTPSA id A083DF970\r
+       for <notmuch@notmuchmail.org>; Thu,  8 Mar 2012 16:39:58 -0500 (EST)\r
+Message-ID: <4F592730.2040908@fifthhorseman.net>\r
+Date: Thu, 08 Mar 2012 16:40:00 -0500\r
+From: Daniel Kahn Gillmor <dkg@fifthhorseman.net>\r
+User-Agent: Mozilla/5.0 (X11; Linux i686; rv:9.0) Gecko/20120125 Icedove/9.0.1\r
+MIME-Version: 1.0\r
+To: notmuch <notmuch@notmuchmail.org>\r
+Subject: Re: Parsing regression with gmime-2.6?\r
+References: <87d38w2e7h.fsf@zancas.localnet>\r
+       <1331058417-13776-1-git-send-email-amdragon@mit.edu>\r
+       <87wr6xmlml.fsf@zancas.localnet>\r
+       <87vcme3kf6.fsf@pip.fifthhorseman.net>\r
+       <874ntybwxv.fsf@servo.finestructure.net>\r
+In-Reply-To: <874ntybwxv.fsf@servo.finestructure.net>\r
+Content-Type: text/plain; charset=UTF-8; format=flowed\r
+Content-Transfer-Encoding: 7bit\r
+X-BeenThere: notmuch@notmuchmail.org\r
+X-Mailman-Version: 2.1.13\r
+Precedence: list\r
+Reply-To: notmuch <notmuch@notmuchmail.org>\r
+List-Id: "Use and development of the notmuch mail system."\r
+       <notmuch.notmuchmail.org>\r
+List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,\r
+       <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>\r
+List-Archive: <http://notmuchmail.org/pipermail/notmuch>\r
+List-Post: <mailto:notmuch@notmuchmail.org>\r
+List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>\r
+List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,\r
+       <mailto:notmuch-request@notmuchmail.org?subject=subscribe>\r
+X-List-Received-Date: Thu, 08 Mar 2012 21:40:01 -0000\r
+\r
+On 03/08/2012 04:32 PM, Jameson Graef Rollins wrote:\r
+\r
+> I actually agree with this position.  mbox files are not proper email\r
+> messages, so if gmime does not explicitly support parsing them then we\r
+> really can't expect it to parse them.\r
+\r
+i think the point here is that gmime used to support parsing them and \r
+now it doesn't.\r
+\r
+So if you've got a pre-existing notmuch index (built from when gmime \r
+*did* parse them) and you're now running notmuch linked against a gmime \r
+that *doesn't* parse them, then notmuch search will produce references \r
+to messages that notmuch show can't produce output for.\r
+\r
+While i appreciate wanting to be sure that we're working with \r
+well-formed files, I don't have a good answer for what the right thing \r
+to do is, if gmime upstream agrees with your assessment of the situation.\r
+\r
+yuck,\r
+\r
+       --dkg\r