From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from localhost (localhost [127.0.0.1]) by olra.theworths.org (Postfix) with ESMTP id 81D9F431FBD for ; Thu, 4 Oct 2012 09:25:11 -0700 (PDT) X-Virus-Scanned: Debian amavisd-new at olra.theworths.org X-Spam-Flag: NO X-Spam-Score: -0.7 X-Spam-Level: X-Spam-Status: No, score=-0.7 tagged_above=-999 required=5 tests=[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 NOJ+YfJEJ6R5 for ; Thu, 4 Oct 2012 09:25:11 -0700 (PDT) Received: from mail-bk0-f53.google.com (mail-bk0-f53.google.com [209.85.214.53]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by olra.theworths.org (Postfix) with ESMTPS id B85CA431FAE for ; Thu, 4 Oct 2012 09:25:10 -0700 (PDT) Received: by mail-bk0-f53.google.com with SMTP id jg15so465247bkc.26 for ; Thu, 04 Oct 2012 09:25:09 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:sender:x-originating-ip:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type :content-transfer-encoding:x-gm-message-state; bh=z+ZkUGRG641dDE/vMvFXfcRfByUePJoBoYiAiW4u+ZU=; b=KE78K4ppDqyMigWhhyBmjbdfXpgGkgsbcONVOituK78UzoXjOjW+2am9VO7C9DfDuZ lCWXN1DVFfdS4wN0s9/aeqSOvDDcwICAyGOOD8yttJIBPfmJXh3jMQEsjoTDVXBgMPE4 cmLv5xWi8/4yXn224vFyDRcGjU+M+eegs2604WhaCBXnNlmKOoI88k+R6Tuk4FcAqEtm b84cFjXo02nlarrNZ4wvC70mcRPWvD2PXo4aNKT8On03APhQbWaAltTJOtBXZfG95UqX MN/m4pbVJvXfjR1CSqou0bi2duW5Qn2J6pn6oFmlv1amLPI0qib0+mzbakcnG9GmVYiM XSKQ== MIME-Version: 1.0 Received: by 10.205.118.135 with SMTP id fq7mr1835620bkc.50.1349367908977; Thu, 04 Oct 2012 09:25:08 -0700 (PDT) Sender: dmitrij.ledkov@surgut.co.uk Received: by 10.205.45.4 with HTTP; Thu, 4 Oct 2012 09:25:08 -0700 (PDT) X-Originating-IP: [86.26.160.15] In-Reply-To: <87vceqh02v.fsf@kiwwwi.com.ar> References: <20121001154309.GE26662@mit.edu> <87vceqh02v.fsf@kiwwwi.com.ar> Date: Thu, 4 Oct 2012 17:25:08 +0100 X-Google-Sender-Auth: ohvYmZEamxUluv0YJ-3O1MwEUo0 Message-ID: Subject: Re: How to index arbitrary headers? From: Dmitrijs Ledkovs To: notmuch@notmuchmail.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Gm-Message-State: ALoCoQkXvNbCtT6eSbEy8d2BdxnaBsL5RkbIyUp9QGKYI4ZjN5g4gjgfQAjZ2vJbG4TDk/Wstse3 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: Thu, 04 Oct 2012 16:25:11 -0000 On 4 October 2012 13:51, Nicol=C3=A1s Reynolds wrote: > Austin Clements writes: > >> 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. > > maybe related: is it possible to index only the headers and not the mail > body? > Checkout project `afew` which pipes complete emails and assigns tags based on the parse result. It may be sufficient for your purpose. Or you can modify notmuch to index the stuff you want. Regards, Dmitrijs.