Return-Path: X-Original-To: notmuch@notmuchmail.org Delivered-To: notmuch@notmuchmail.org Received: from localhost (localhost [127.0.0.1]) by olra.theworths.org (Postfix) with ESMTP id 98F12431FAF for ; Wed, 3 Oct 2012 11:32:32 -0700 (PDT) X-Virus-Scanned: Debian amavisd-new at olra.theworths.org X-Spam-Flag: NO X-Spam-Score: -0.699 X-Spam-Level: X-Spam-Status: No, score=-0.699 tagged_above=-999 required=5 tests=[HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=disabled Received: from olra.theworths.org ([127.0.0.1]) by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CnJCdL26sae3 for ; Wed, 3 Oct 2012 11:32:31 -0700 (PDT) Received: from mail-vb0-f53.google.com (mail-vb0-f53.google.com [209.85.212.53]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by olra.theworths.org (Postfix) with ESMTPS id D24B4431FAE for ; Wed, 3 Oct 2012 11:32:31 -0700 (PDT) Received: by vbbfc21 with SMTP id fc21so8577509vbb.26 for ; Wed, 03 Oct 2012 11:32:31 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:cc:content-type:x-gm-message-state; bh=/DBWPqwqhYD2Tm3A8NIpuJjd5XmC+cU+LjlwuU3tf/4=; b=Xfs74vhoGKAqAkSmg8SW5Zq5KqaowY+lf+ktNHfelTZ/jUwpq40xKeXHw4G38HAh88 wZsVr9Zk2eHsBfcDTVnG7y68TbZ2/U5BRkE1yU6ZsW2vZ76xScLUfe970f47CiVgW/g5 YYEprvF/aeOS6F0SnWk9v3vFw3dyp7DF7+2KB9vaEX2Wvk3bzx5RaSGD0AETv8hLrhon EyLXFNUsS38PDPogEpWuUN7zS7JVM5TzjaEnex3zEakSDIaUStSr/rCkds0YnS4cTxQ1 s+wp/bX+KdTD6UM0Sxw1NFj+gptzwGRmHoqDO9HlKWKMovShV7NqwlzwH2LUnroYbL4B 6b7w== MIME-Version: 1.0 Received: by 10.52.174.82 with SMTP id bq18mr1362106vdc.25.1349289151127; Wed, 03 Oct 2012 11:32:31 -0700 (PDT) Received: by 10.58.94.136 with HTTP; Wed, 3 Oct 2012 11:32:30 -0700 (PDT) X-Originating-IP: [91.155.82.121] In-Reply-To: <20121001154309.GE26662@mit.edu> References: <20121001154309.GE26662@mit.edu> Date: Wed, 3 Oct 2012 21:32:30 +0300 Message-ID: Subject: Re: How to index arbitrary headers? From: Petri Savolainen To: Austin Clements Content-Type: multipart/alternative; boundary=bcaec51ba61b8d606f04cb2bdca2 X-Gm-Message-State: ALoCoQnlDCHIq2QupaRcpy9DS5tTlRTPOzZKVjwl/hO7bYNAIx8OHIsEJis1JJm9JpUkcZZc2+wX X-Mailman-Approved-At: Wed, 03 Oct 2012 22:58:24 -0700 Cc: notmuch@notmuchmail.org X-BeenThere: notmuch@notmuchmail.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: "Use and development of the notmuch mail system." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Oct 2012 18:32:32 -0000 --bcaec51ba61b8d606f04cb2bdca2 Content-Type: text/plain; charset=ISO-8859-1 Hi, thanks for your response. I am evaluating notmuch / xapian for building an application for analyzing in various ways a fairly large number of emails accumulated over several years. I am afraid the number of headers that would ultimately need to be indexed is therefore quite a lot larger than what notmuch currently indexes. Petri 2012/10/1 Austin Clements > Quoth Petri Savolainen on Oct 01 at 3:39 pm: > > Hello, > > I could not find information anywhere in notmuch docs about what is > > actually indexed - specifically, what email headers are indexed and > > searchable? If a header is not indexed, does searching for its value > still > > result in a search hit? > > It would be nice if one could just provide the list of headers to be > > indexed in some configuration file or something. > > Thanks, > > Petri > > notmuch doesn't currently implement this, though it is an > oft-requested feature. One (not insurmountable) difficulty is that > the database would have to be rebuilt if a user-configured list of > headers changed and there are technical limitations that prevent us > from simply indexing all headers. Out of curiosity, what headers are > you interested in indexing? > > The currently indexed headers are described in man > notmuch-search-terms. > --bcaec51ba61b8d606f04cb2bdca2 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi,

thanks for your response.=A0I am evaluating notmuch = / xapian for building an application for analyzing in various ways a fairly= large number of emails accumulated over several years. I am afraid the num= ber of headers that would ultimately need to be indexed is therefore quite = a lot larger than what notmuch currently indexes.

=A0Petri

2012/= 10/1 Austin Clements <amdragon@mit.edu>
Quoth Petri Savolainen on Oct 01 at =A03:39 pm:
> =A0 =A0Hello,
> =A0 =A0I could not find information anywhere in notmuch docs about wha= t is
> =A0 =A0actually indexed - specifically, what email headers are indexed= and
> =A0 =A0searchable? If a header is not indexed, does searching for its = value still
> =A0 =A0result in a search hit?
> =A0 =A0It would be nice if one could just provide the list of headers = to be
> =A0 =A0indexed in some configuration file or something.
> =A0 =A0Thanks,
> =A0 =A0=A0Petri

notmuch doesn't currently implement this, though it is an oft-requested feature. =A0One (not insurmountable) difficulty is that
the database would have to be rebuilt if a user-configured list of
headers changed and there are technical limitations that prevent us
from simply indexing all headers. =A0Out of curiosity, what headers are
you interested in indexing?

The currently indexed headers are described in man
notmuch-search-terms.

--bcaec51ba61b8d606f04cb2bdca2--