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 9FBE2431FCF for ; Mon, 16 Mar 2015 04:36:43 -0700 (PDT) X-Virus-Scanned: Debian amavisd-new at olra.theworths.org X-Spam-Flag: NO X-Spam-Score: 2.438 X-Spam-Level: ** X-Spam-Status: No, score=2.438 tagged_above=-999 required=5 tests=[DNS_FROM_AHBL_RHSBL=2.438] 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 q-4HJeHD9tJ4 for ; Mon, 16 Mar 2015 04:36:40 -0700 (PDT) Received: from mx.xen14.node3324.gplhost.com (gitolite.debian.net [87.98.215.224]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by olra.theworths.org (Postfix) with ESMTPS id 5E336431FB6 for ; Mon, 16 Mar 2015 04:36:40 -0700 (PDT) Received: from remotemail by mx.xen14.node3324.gplhost.com with local (Exim 4.80) (envelope-from ) id 1YXTJE-0000uv-PW; Mon, 16 Mar 2015 11:35:48 +0000 Received: (nullmailer pid 7965 invoked by uid 1000); Mon, 16 Mar 2015 11:35:35 -0000 From: David Bremner To: Harlan Lieberman-Berg , notmuch@notmuchmail.org Subject: Re: Proposal: List-Id In-Reply-To: <87wq2huan3.fsf@setec.io> References: <87wq2huan3.fsf@setec.io> User-Agent: Notmuch/0.19+67~gdbe9924 (http://notmuchmail.org) Emacs/24.4.1 (x86_64-pc-linux-gnu) Date: Mon, 16 Mar 2015 12:35:35 +0100 Message-ID: <878uex2n08.fsf@maritornes.cs.unb.ca> MIME-Version: 1.0 Content-Type: text/plain 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: Mon, 16 Mar 2015 11:36:43 -0000 Harlan Lieberman-Berg writes: > > The standard for identifying mailing lists seems to be List-Id, as per > RFC 2919. I can understand the desire to keep the number of headers > included in the header block low, but I wonder if this might be a common > enough use-case to suggest its inclusion. > I think the real blocker at this point is that some copies of a message may have list-id header and some not. Currently we only index the first copy of a message that arrives. Indexing all copies would probably be a good step in any case, but e.g. handling deletion of files requires some care in that case. d