Re: notmuch should search on date received

diff --git a/30/db47f6f5e4847c78f58b248e7ac1e62ade5219 b/30/db47f6f5e4847c78f58b248e7ac1e62ade5219
new file mode 100644 (file)
index 0000000..1c64c4e
--- /dev/null
+++ b/30/db47f6f5e4847c78f58b248e7ac1e62ade5219
@@ -0,0 +1,97 @@
+Return-Path: <error4me@gmx.de>\r
+X-Original-To: notmuch@notmuchmail.org\r
+Delivered-To: notmuch@notmuchmail.org\r
+Received: from localhost (localhost [127.0.0.1])\r
+ by arlo.cworth.org (Postfix) with ESMTP id 322126DE0A9A\r
+ for <notmuch@notmuchmail.org>; Tue,  5 May 2015 09:59:16 -0700 (PDT)\r
+X-Virus-Scanned: Debian amavisd-new at cworth.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: 0.019\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=0.019 tagged_above=-999 required=5\r
+ tests=[FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001,\r
+ RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001,\r
+ T_FREEMAIL_FORGED_FROMDOMAIN=0.01,\r
+ T_HEADER_FROM_DIFFERENT_DOMAINS=0.01] autolearn=disabled\r
+Received: from arlo.cworth.org ([127.0.0.1])\r
+ by localhost (arlo.cworth.org [127.0.0.1]) (amavisd-new, port 10024)\r
+ with ESMTP id 4UVGP9hbchCS for <notmuch@notmuchmail.org>;\r
+ Tue,  5 May 2015 09:59:13 -0700 (PDT)\r
+Received: from mout.gmx.net (mout.gmx.net [212.227.17.20])\r
+ by arlo.cworth.org (Postfix) with ESMTPS id A2DB56DE1006\r
+ for <notmuch@notmuchmail.org>; Tue,  5 May 2015 09:59:12 -0700 (PDT)\r
+Received: from boo.workgroup ([91.64.233.152]) by mail.gmx.com (mrgmx102) with\r
+ ESMTPSA (Nemesis) id 0LZlZ2-1ZWPOj45ym-00lYeR for\r
+ <notmuch@notmuchmail.org>; Tue, 05 May 2015 18:59:10 +0200\r
+Received: from grfz by boo.workgroup with local (Exim 4.84)\r
+ (envelope-from <error4me@gmx.de>)\r
+ id 1YpgBS-0002eb-Mr; Tue, 05 May 2015 18:59:02 +0200\r
+Date: Tue, 5 May 2015 18:58:32 +0200\r
+From: Gregor Zattler <telegraph@gmx.net>\r
+To: notmuch <notmuch@notmuchmail.org>\r
+Subject: Re: notmuch should search on date received\r
+Message-ID: <20150505165832.GA20025@boo.workgroup>\r
+Mail-Followup-To: notmuch <notmuch@notmuchmail.org>\r
+References: <20150503101412.GB25636@boo.workgroup>\r
+ <87pp6gagvx.fsf@maritornes.cs.unb.ca>\r
+MIME-Version: 1.0\r
+Content-Type: text/plain; charset=utf-8\r
+Content-Disposition: inline\r
+Content-Transfer-Encoding: 8bit\r
+In-Reply-To: <87pp6gagvx.fsf@maritornes.cs.unb.ca>\r
+User-Agent: Mutt/1.5.23 (2014-03-12)\r
+Sender: error4me@gmx.de\r
+X-Provags-ID: V03:K0:6UPvkyQiNmD6W4Lqhy2dQuCiwBPLbLnPJw891pBx+CF2iJOY6qE\r
+ I2IcAw/DsleQQjfr5Aizw1MwyoT6gN9zYYjmoAOYEyum+eEFn2+YL9/KVJpBDQy4ziaHTaY\r
+ EDPlfZk+BM0WxXtwnLTEAX7MrZTrfk/RvBa0b6iilz7RV2Yo8lKDahfQlgQhTMh6oVjwgeq\r
+ tF9taBdXLpaEAGStd1S/g==\r
+X-UI-Out-Filterresults: notjunk:1;\r
+X-BeenThere: notmuch@notmuchmail.org\r
+X-Mailman-Version: 2.1.18\r
+Precedence: list\r
+List-Id: "Use and development of the notmuch mail system."\r
+ <notmuch.notmuchmail.org>\r
+List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,\r
+ <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>\r
+List-Archive: <http://notmuchmail.org/pipermail/notmuch/>\r
+List-Post: <mailto:notmuch@notmuchmail.org>\r
+List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>\r
+List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,\r
+ <mailto:notmuch-request@notmuchmail.org?subject=subscribe>\r
+X-List-Received-Date: Tue, 05 May 2015 16:59:16 -0000\r
+\r
+Hi David,\r
+* David Bremner <david@tethera.net> [04. May. 2015]:\r
+> Gregor Zattler <telegraph@gmx.net> writes:\r
+>> I wished notmuch could search on (the top most) Received: -header\r
+>> since not all emails have correct Date: -headers.\r
+>>\r
+>> Rationale: Show all emails since yesterday…  This is immensely\r
+>> important for my work flow.\r
+> \r
+> These are two somewhat different requests. Being able to search on the\r
+> Received headers would involve a usual kind of term search, but not date\r
+> searching.\r
+\r
+This way one could at least search for years but it would not be\r
+convenient. \r
+\r
+> This might be problematic as a default because of the volume\r
+> of received headers.  In order to use it for date search, it would need\r
+> to be parsed for data information and either override the Date:-header\r
+> or provide a second prefix like received-date.\r
+\r
+This is what I wish for.  There are several Received: -headers,\r
+the top most contains the actual moment when the email arrived on\r
+the system.  I would like to search for date ranges of arrival.\r
+\r
+\r
+> Or maybe a single\r
+> message could have multiple date: prefixed terms, I'm not sure.\r
+\r
+This I don’t understand.\r
+\r
+\r
+Ciao, Gregor\r
+-- \r
+ -... --- .-. . -.. ..--.. ...-.-\r