Re: How to index arbitrary headers?

diff --git a/3c/874aee1d826dafe45adcb8c0930bf0b57140bf b/3c/874aee1d826dafe45adcb8c0930bf0b57140bf
new file mode 100644 (file)
index 0000000..e246096
--- /dev/null
+++ b/3c/874aee1d826dafe45adcb8c0930bf0b57140bf
@@ -0,0 +1,148 @@
+Return-Path: <petri@koodaamo.fi>\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 98F12431FAF\r
+       for <notmuch@notmuchmail.org>; Wed,  3 Oct 2012 11:32:32 -0700 (PDT)\r
+X-Virus-Scanned: Debian amavisd-new at olra.theworths.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: -0.699\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=-0.699 tagged_above=-999 required=5\r
+       tests=[HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] 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 CnJCdL26sae3 for <notmuch@notmuchmail.org>;\r
+       Wed,  3 Oct 2012 11:32:31 -0700 (PDT)\r
+Received: from mail-vb0-f53.google.com (mail-vb0-f53.google.com\r
+       [209.85.212.53]) (using TLSv1 with cipher RC4-SHA (128/128 bits))\r
+       (No client certificate requested)\r
+       by olra.theworths.org (Postfix) with ESMTPS id D24B4431FAE\r
+       for <notmuch@notmuchmail.org>; Wed,  3 Oct 2012 11:32:31 -0700 (PDT)\r
+Received: by vbbfc21 with SMTP id fc21so8577509vbb.26\r
+       for <notmuch@notmuchmail.org>; Wed, 03 Oct 2012 11:32:31 -0700 (PDT)\r
+X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;\r
+       d=google.com; s=20120113;\r
+       h=mime-version:x-originating-ip:in-reply-to:references:date\r
+       :message-id:subject:from:to:cc:content-type:x-gm-message-state;\r
+       bh=/DBWPqwqhYD2Tm3A8NIpuJjd5XmC+cU+LjlwuU3tf/4=;\r
+       b=Xfs74vhoGKAqAkSmg8SW5Zq5KqaowY+lf+ktNHfelTZ/jUwpq40xKeXHw4G38HAh88\r
+       wZsVr9Zk2eHsBfcDTVnG7y68TbZ2/U5BRkE1yU6ZsW2vZ76xScLUfe970f47CiVgW/g5\r
+       YYEprvF/aeOS6F0SnWk9v3vFw3dyp7DF7+2KB9vaEX2Wvk3bzx5RaSGD0AETv8hLrhon\r
+       EyLXFNUsS38PDPogEpWuUN7zS7JVM5TzjaEnex3zEakSDIaUStSr/rCkds0YnS4cTxQ1\r
+       s+wp/bX+KdTD6UM0Sxw1NFj+gptzwGRmHoqDO9HlKWKMovShV7NqwlzwH2LUnroYbL4B\r
+       6b7w==\r
+MIME-Version: 1.0\r
+Received: by 10.52.174.82 with SMTP id bq18mr1362106vdc.25.1349289151127; Wed,\r
+       03 Oct 2012 11:32:31 -0700 (PDT)\r
+Received: by 10.58.94.136 with HTTP; Wed, 3 Oct 2012 11:32:30 -0700 (PDT)\r
+X-Originating-IP: [91.155.82.121]\r
+In-Reply-To: <20121001154309.GE26662@mit.edu>\r
+References:\r
+ <CACXwgK9bmyqUMmw9LNhqc7o86_LXx8agQByusBiQt_wRbQ8O=w@mail.gmail.com>\r
+       <20121001154309.GE26662@mit.edu>\r
+Date: Wed, 3 Oct 2012 21:32:30 +0300\r
+Message-ID:\r
+ <CACXwgK8Any3Cd+eO21Frz2X8P1kcOkw9XDTN5jj1Nu-DQdHRUg@mail.gmail.com>\r
+Subject: Re: How to index arbitrary headers?\r
+From: Petri Savolainen <petri@koodaamo.fi>\r
+To: Austin Clements <amdragon@mit.edu>\r
+Content-Type: multipart/alternative; boundary=bcaec51ba61b8d606f04cb2bdca2\r
+X-Gm-Message-State:\r
+ ALoCoQnlDCHIq2QupaRcpy9DS5tTlRTPOzZKVjwl/hO7bYNAIx8OHIsEJis1JJm9JpUkcZZc2+wX\r
+X-Mailman-Approved-At: Wed, 03 Oct 2012 22:58:24 -0700\r
+Cc: notmuch@notmuchmail.org\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: Wed, 03 Oct 2012 18:32:32 -0000\r
+\r
+--bcaec51ba61b8d606f04cb2bdca2\r
+Content-Type: text/plain; charset=ISO-8859-1\r
+\r
+Hi,\r
+\r
+thanks for your response. I am evaluating notmuch / xapian for building an\r
+application for analyzing in various ways a fairly large number of emails\r
+accumulated over several years. I am afraid the number of headers that\r
+would ultimately need to be indexed is therefore quite a lot larger than\r
+what notmuch currently indexes.\r
+\r
+ Petri\r
+\r
+2012/10/1 Austin Clements <amdragon@mit.edu>\r
+\r
+> Quoth Petri Savolainen on Oct 01 at  3:39 pm:\r
+> >    Hello,\r
+> >    I could not find information anywhere in notmuch docs about what is\r
+> >    actually indexed - specifically, what email headers are indexed and\r
+> >    searchable? If a header is not indexed, does searching for its value\r
+> still\r
+> >    result in a search hit?\r
+> >    It would be nice if one could just provide the list of headers to be\r
+> >    indexed in some configuration file or something.\r
+> >    Thanks,\r
+> >     Petri\r
+>\r
+> notmuch doesn't currently implement this, though it is an\r
+> oft-requested feature.  One (not insurmountable) difficulty is that\r
+> the database would have to be rebuilt if a user-configured list of\r
+> headers changed and there are technical limitations that prevent us\r
+> from simply indexing all headers.  Out of curiosity, what headers are\r
+> you interested in indexing?\r
+>\r
+> The currently indexed headers are described in man\r
+> notmuch-search-terms.\r
+>\r
+\r
+--bcaec51ba61b8d606f04cb2bdca2\r
+Content-Type: text/html; charset=ISO-8859-1\r
+Content-Transfer-Encoding: quoted-printable\r
+\r
+Hi,<div><br></div><div>thanks for your response.=A0I am evaluating notmuch =\r
+/ xapian for building an application for analyzing in various ways a fairly=\r
+ large number of emails accumulated over several years. I am afraid the num=\r
+ber of headers that would ultimately need to be indexed is therefore quite =\r
+a lot larger than what notmuch currently indexes.</div>\r
+<div><br></div><div>=A0Petri</div><div><br><div class=3D"gmail_quote">2012/=\r
+10/1 Austin Clements <span dir=3D"ltr">&lt;<a href=3D"mailto:amdragon@mit.e=\r
+du" target=3D"_blank">amdragon@mit.edu</a>&gt;</span><br><blockquote class=\r
+=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padd=\r
+ing-left:1ex">\r
+Quoth Petri Savolainen on Oct 01 at =A03:39 pm:<br>\r
+<div><div class=3D"h5">&gt; =A0 =A0Hello,<br>\r
+&gt; =A0 =A0I could not find information anywhere in notmuch docs about wha=\r
+t is<br>\r
+&gt; =A0 =A0actually indexed - specifically, what email headers are indexed=\r
+ and<br>\r
+&gt; =A0 =A0searchable? If a header is not indexed, does searching for its =\r
+value still<br>\r
+&gt; =A0 =A0result in a search hit?<br>\r
+&gt; =A0 =A0It would be nice if one could just provide the list of headers =\r
+to be<br>\r
+&gt; =A0 =A0indexed in some configuration file or something.<br>\r
+&gt; =A0 =A0Thanks,<br>\r
+&gt; =A0 =A0=A0Petri<br>\r
+<br>\r
+</div></div>notmuch doesn&#39;t currently implement this, though it is an<b=\r
+r>\r
+oft-requested feature. =A0One (not insurmountable) difficulty is that<br>\r
+the database would have to be rebuilt if a user-configured list of<br>\r
+headers changed and there are technical limitations that prevent us<br>\r
+from simply indexing all headers. =A0Out of curiosity, what headers are<br>\r
+you interested in indexing?<br>\r
+<br>\r
+The currently indexed headers are described in man<br>\r
+notmuch-search-terms.<br>\r
+</blockquote></div><br></div>\r
+\r
+--bcaec51ba61b8d606f04cb2bdca2--\r