Re: Parsing regression with gmime-2.6?

diff --git a/e9/c2c31308d84a651291d6be4bbdeb27232eb735 b/e9/c2c31308d84a651291d6be4bbdeb27232eb735
new file mode 100644 (file)
index 0000000..378a293
--- /dev/null
+++ b/e9/c2c31308d84a651291d6be4bbdeb27232eb735
@@ -0,0 +1,111 @@
+Return-Path: <jrollins@finestructure.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 2A2A9431FB6\r
+       for <notmuch@notmuchmail.org>; Thu,  8 Mar 2012 13:59:22 -0800 (PST)\r
+X-Virus-Scanned: Debian amavisd-new at olra.theworths.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: -2.29\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=-2.29 tagged_above=-999 required=5\r
+       tests=[RCVD_IN_DNSWL_MED=-2.3, T_MIME_NO_TEXT=0.01] 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 PEdOAttgRmAz for <notmuch@notmuchmail.org>;\r
+       Thu,  8 Mar 2012 13:59:21 -0800 (PST)\r
+Received: from outgoing-mail.its.caltech.edu (outgoing-mail.its.caltech.edu\r
+       [131.215.239.19])\r
+       by olra.theworths.org (Postfix) with ESMTP id 8B96F431FAE\r
+       for <notmuch@notmuchmail.org>; Thu,  8 Mar 2012 13:59:21 -0800 (PST)\r
+Received: from fire-doxen.imss.caltech.edu (localhost [127.0.0.1])\r
+       by fire-doxen-postvirus (Postfix) with ESMTP id 051302E50D70;\r
+       Thu,  8 Mar 2012 13:59:19 -0800 (PST)\r
+X-Spam-Scanned: at Caltech-IMSS on fire-doxen by amavisd-new\r
+Received: from finestructure.net (DHCP-123-180.caltech.edu [131.215.123.180])\r
+       (Authenticated sender: jrollins)\r
+       by fire-doxen-submit (Postfix) with ESMTP id 3DAF92E50D80;\r
+       Thu,  8 Mar 2012 13:59:16 -0800 (PST)\r
+Received: by finestructure.net (Postfix, from userid 1000)\r
+       id F127F9DE; Thu,  8 Mar 2012 13:59:15 -0800 (PST)\r
+From: Jameson Graef Rollins <jrollins@finestructure.net>\r
+To: Daniel Kahn Gillmor <dkg@fifthhorseman.net>,\r
+       notmuch <notmuch@notmuchmail.org>\r
+Subject: Re: Parsing regression with gmime-2.6?\r
+In-Reply-To: <4F592730.2040908@fifthhorseman.net>\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
+       <4F592730.2040908@fifthhorseman.net>\r
+User-Agent: Notmuch/0.11.1+266~gadb05cc (http://notmuchmail.org) Emacs/23.3.1\r
+       (x86_64-pc-linux-gnu)\r
+Date: Thu, 08 Mar 2012 13:59:13 -0800\r
+Message-ID: <87vcmeah5a.fsf@servo.finestructure.net>\r
+MIME-Version: 1.0\r
+Content-Type: multipart/signed; boundary="=-=-=";\r
+       micalg=pgp-sha256; protocol="application/pgp-signature"\r
+X-BeenThere: notmuch@notmuchmail.org\r
+X-Mailman-Version: 2.1.13\r
+Precedence: list\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:59:22 -0000\r
+\r
+--=-=-=\r
+Content-Transfer-Encoding: quoted-printable\r
+\r
+On Thu, 08 Mar 2012 16:40:00 -0500, Daniel Kahn Gillmor <dkg@fifthhorseman.=\r
+net> wrote:\r
+> i think the point here is that gmime used to support parsing them and=20\r
+> now it doesn't.\r
+>=20\r
+> So if you've got a pre-existing notmuch index (built from when gmime=20\r
+> *did* parse them) and you're now running notmuch linked against a gmime=20\r
+> that *doesn't* parse them, then notmuch search will produce references=20\r
+> to messages that notmuch show can't produce output for.\r
+\r
+This is unfortunate for those that suffer from this but again I don't\r
+think the solution is a partial parsing of mbox files.\r
+\r
+If this really is the situation, it seems like the *previous* behavior\r
+was actually the problematic one, which has now been fixed, even though\r
+it appears to be a regression.\r
+\r
+I think I would argue that users who do fall in to this situation should\r
+just simply convert all of their mbox files into proper messages.\r
+That's the position that we've actually held all along: notmuch does not\r
+support mbox and those with mbox files should just convert them to\r
+individual messages with something like mbox2maildir or the like.\r
+\r
+jamie.\r
+\r
+--=-=-=\r
+Content-Type: application/pgp-signature\r
+\r
+-----BEGIN PGP SIGNATURE-----\r
+Version: GnuPG v1.4.11 (GNU/Linux)\r
+\r
+iQIcBAEBCAAGBQJPWSuxAAoJEO00zqvie6q8qrsQAKwlHDgTo6PmIuGR+Demz9KX\r
+KcrkGTOqFSoHvvOX/VYDm1PiEE2JLI5c19gvLE/1kGMaluUIIm7TzclWBRvTdv4b\r
+1cK4eioJGE6eifXvTKcyfJr8/O4CXIkIFw3+3F3xjFEibx1o48u5HwRyvtOa4wjQ\r
+IKRADSgbigzyI4intd0V4Ki3f/qI1wS8gTtrZt6lhH1P1dBNbOp+oBPJ3+wyIOR9\r
+BbTHiiQ3SvrCodkPuucD9xz83xIaxVzgXRsWnD1nwR2KgMzlRMP10bqbUto6anQF\r
+Bh2hUJP+OR+lZIgrkk4MTOS4/HKTc7lFkHiiUkoud/OYH/v/DNp2vFKoun1PT69P\r
+qBlYvVoVttFxfaUn7wSIM7d9S09d0rfWLPkgYNpNCmdhdGDANeocD1SX2dK0dMtv\r
+PZkezbICF3WPT1yheQrn5bkjvfS/eDd6xSV+JiZkGdMoe8rPe+/ofchZ9hA32CUf\r
+wqn3IAdtF49Rod9KIoNU4DBTh9F9pbwG0HX3FGX7XA3CgSbSm3YO3HDVjvAb2w7K\r
+MbmJSzjrO8h+GqCGH6+0sJWpEmmM9j0NYTi/4TFhq09MjIwX1tg+ww176By5loq2\r
+/EiASkRV+1xwvRKa3nPHCxlPh0DhQeSBxX7Hua+GkeIkVf1tTkgcRG9gKt4Sf4Iq\r
+1fX4xgxNZoz+4aLNwvZD\r
+=5ZSY\r
+-----END PGP SIGNATURE-----\r
+--=-=-=--\r