From a42f49ac6f389e2fc7d1c9702173d6a57ab0c4da Mon Sep 17 00:00:00 2001 From: Gregor Zattler Date: Tue, 5 May 2015 18:58:32 +0200 Subject: [PATCH] Re: notmuch should search on date received --- 30/db47f6f5e4847c78f58b248e7ac1e62ade5219 | 97 +++++++++++++++++++++++ 1 file changed, 97 insertions(+) create mode 100644 30/db47f6f5e4847c78f58b248e7ac1e62ade5219 diff --git a/30/db47f6f5e4847c78f58b248e7ac1e62ade5219 b/30/db47f6f5e4847c78f58b248e7ac1e62ade5219 new file mode 100644 index 000000000..1c64c4eef --- /dev/null +++ b/30/db47f6f5e4847c78f58b248e7ac1e62ade5219 @@ -0,0 +1,97 @@ +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 322126DE0A9A + for ; Tue, 5 May 2015 09:59:16 -0700 (PDT) +X-Virus-Scanned: Debian amavisd-new at cworth.org +X-Spam-Flag: NO +X-Spam-Score: 0.019 +X-Spam-Level: +X-Spam-Status: No, score=0.019 tagged_above=-999 required=5 + tests=[FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, + RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, + T_FREEMAIL_FORGED_FROMDOMAIN=0.01, + T_HEADER_FROM_DIFFERENT_DOMAINS=0.01] 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 4UVGP9hbchCS for ; + Tue, 5 May 2015 09:59:13 -0700 (PDT) +Received: from mout.gmx.net (mout.gmx.net [212.227.17.20]) + by arlo.cworth.org (Postfix) with ESMTPS id A2DB56DE1006 + for ; Tue, 5 May 2015 09:59:12 -0700 (PDT) +Received: from boo.workgroup ([91.64.233.152]) by mail.gmx.com (mrgmx102) with + ESMTPSA (Nemesis) id 0LZlZ2-1ZWPOj45ym-00lYeR for + ; Tue, 05 May 2015 18:59:10 +0200 +Received: from grfz by boo.workgroup with local (Exim 4.84) + (envelope-from ) + id 1YpgBS-0002eb-Mr; Tue, 05 May 2015 18:59:02 +0200 +Date: Tue, 5 May 2015 18:58:32 +0200 +From: Gregor Zattler +To: notmuch +Subject: Re: notmuch should search on date received +Message-ID: <20150505165832.GA20025@boo.workgroup> +Mail-Followup-To: notmuch +References: <20150503101412.GB25636@boo.workgroup> + <87pp6gagvx.fsf@maritornes.cs.unb.ca> +MIME-Version: 1.0 +Content-Type: text/plain; charset=utf-8 +Content-Disposition: inline +Content-Transfer-Encoding: 8bit +In-Reply-To: <87pp6gagvx.fsf@maritornes.cs.unb.ca> +User-Agent: Mutt/1.5.23 (2014-03-12) +Sender: error4me@gmx.de +X-Provags-ID: V03:K0:6UPvkyQiNmD6W4Lqhy2dQuCiwBPLbLnPJw891pBx+CF2iJOY6qE + I2IcAw/DsleQQjfr5Aizw1MwyoT6gN9zYYjmoAOYEyum+eEFn2+YL9/KVJpBDQy4ziaHTaY + EDPlfZk+BM0WxXtwnLTEAX7MrZTrfk/RvBa0b6iilz7RV2Yo8lKDahfQlgQhTMh6oVjwgeq + tF9taBdXLpaEAGStd1S/g== +X-UI-Out-Filterresults: notjunk:1; +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: Tue, 05 May 2015 16:59:16 -0000 + +Hi David, +* David Bremner [04. May. 2015]: +> Gregor Zattler writes: +>> 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… 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 way one could at least search for years but it would not be +convenient. + +> 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. + +This is what I wish for. There are several Received: -headers, +the top most contains the actual moment when the email arrived on +the system. I would like to search for date ranges of arrival. + + +> Or maybe a single +> message could have multiple date: prefixed terms, I'm not sure. + +This I don’t understand. + + +Ciao, Gregor +-- + -... --- .-. . -.. ..--.. ...-.- -- 2.26.2