Return-Path: X-Original-To: notmuch@notmuchmail.org Delivered-To: notmuch@notmuchmail.org Received: from localhost (localhost [127.0.0.1]) by arlo.cworth.org (Postfix) with ESMTP id 32A9D6DE1919 for ; Mon, 4 May 2015 01:26:53 -0700 (PDT) X-Virus-Scanned: Debian amavisd-new at cworth.org X-Spam-Flag: NO X-Spam-Score: 0.319 X-Spam-Level: X-Spam-Status: No, score=0.319 tagged_above=-999 required=5 tests=[AWL=0.319] autolearn=disabled Received: from arlo.cworth.org ([127.0.0.1]) by localhost (arlo.cworth.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2T5HafWB9crf for ; Mon, 4 May 2015 01:26:51 -0700 (PDT) Received: from mx.xen14.node3324.gplhost.com (gitolite.debian.net [87.98.215.224]) by arlo.cworth.org (Postfix) with ESMTPS id D2BAE6DE1917 for ; Mon, 4 May 2015 01:26:50 -0700 (PDT) Received: from remotemail by mx.xen14.node3324.gplhost.com with local (Exim 4.80) (envelope-from ) id 1YpBhF-0002Bs-F1; Mon, 04 May 2015 08:25:49 +0000 Received: (nullmailer pid 27005 invoked by uid 1000); Mon, 04 May 2015 08:25:38 -0000 From: David Bremner To: Gregor Zattler , notmuch Subject: Re: [bug] [wish] notmuch should search on date received In-Reply-To: <20150503101412.GB25636@boo.workgroup> References: <20150503101412.GB25636@boo.workgroup> User-Agent: Notmuch/0.19+96~g703c8f9 (http://notmuchmail.org) Emacs/24.4.1 (x86_64-pc-linux-gnu) Date: Mon, 04 May 2015 10:25:38 +0200 Message-ID: <87pp6gagvx.fsf@maritornes.cs.unb.ca> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: notmuch@notmuchmail.org X-Mailman-Version: 2.1.18 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, 04 May 2015 08:26:53 -0000 Gregor Zattler writes: > Dear notmuch developers, > > I wished notmuch could search on (the top most) Received: -header > since not all emails have correct Date: -headers. > > Rationale: Show all emails since yesterday=E2=80=A6 This is immensely > important for my work flow. These are two somewhat different requests. Being able to search on the Received headers would involve a usual kind of term search, but not date searching. This might be problematic as a default because of the volume of received headers. In order to use it for date search, it would need to be parsed for data information and either override the Date:-header or provide a second prefix like received-date. Or maybe a single message could have multiple date: prefixed terms, I'm not sure. d