RE: email snoozing in notmuch

diff --git a/aa/6363a49572a4a8bffb881f65dd1c5942d90c72 b/aa/6363a49572a4a8bffb881f65dd1c5942d90c72
new file mode 100644 (file)
index 0000000..a33cd8b
--- /dev/null
+++ b/aa/6363a49572a4a8bffb881f65dd1c5942d90c72
@@ -0,0 +1,120 @@
+Return-Path: <alpine.art.de@gmail.com>\r
+X-Original-To: notmuch@notmuchmail.org\r
+Delivered-To: notmuch@notmuchmail.org\r
+Received: from localhost (localhost [127.0.0.1])\r
+       by olra.theworths.org (Postfix) with ESMTP id 17270431FDA\r
+       for <notmuch@notmuchmail.org>; Wed, 10 Dec 2014 00:13:58 -0800 (PST)\r
+X-Virus-Scanned: Debian amavisd-new at olra.theworths.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: -0.799\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=-0.799 tagged_above=-999 required=5\r
+       tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1,\r
+       FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=disabled\r
+Received: from olra.theworths.org ([127.0.0.1])\r
+       by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)\r
+       with ESMTP id t+WFJlPdUHbf for <notmuch@notmuchmail.org>;\r
+       Wed, 10 Dec 2014 00:13:53 -0800 (PST)\r
+Received: from mail-wg0-f49.google.com (mail-wg0-f49.google.com\r
+ [74.125.82.49])       (using TLSv1 with cipher RC4-SHA (128/128 bits))        (No client\r
+ certificate requested)        by olra.theworths.org (Postfix) with ESMTPS id\r
+ 9D1DA431FC3   for <notmuch@notmuchmail.org>; Wed, 10 Dec 2014 00:13:53 -0800\r
+ (PST)\r
+Received: by mail-wg0-f49.google.com with SMTP id n12so2885914wgh.8\r
+       for <notmuch@notmuchmail.org>; Wed, 10 Dec 2014 00:13:52 -0800 (PST)\r
+DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;\r
+       h=date:from:to:cc:message-id:in-reply-to:references:subject\r
+       :mime-version:content-type:content-transfer-encoding:attach;\r
+       bh=Ynvi6iuJSgazzoPCaoOOITFLbewfs+nT6XD8GFzMYT4=;\r
+       b=WaGDuotOe0HrHW0BqmoJ17vNVe8Yhog3I2v3WOa6UfOWCijbAHMj2I+ZDEj+nGXyyn\r
+       IGLP4xAzicIZ3y34gQJk/cH6gkDLJQrsUFcD3JW4cYboWIqwphm/fvftQnBE4xQmNi9N\r
+       MVG/LYazJuUCccJqQQH696apA+2O9c+RP+uSLUVHoOj5vF+jxNuTxnHg/BjOUojc1NLm\r
+       eT4HmvPnT/oSa7DRg4i4Oo0IxDTOqGFUq/jjwE/G/g6nuEh8ch5saeoMEmcFn9LtdTY6\r
+       8WjR6TVYZ3hHosP78z42qWJw6/iFir9dTi4chsUBO2hFkBMC6oHAd+fi3LszmEQWXTiV\r
+       xeMw==\r
+X-Received: by 10.180.72.199 with SMTP id f7mr4105176wiv.53.1418199232392;\r
+       Wed, 10 Dec 2014 00:13:52 -0800 (PST)\r
+Received: from localhost (p4FFB8E50.dip0.t-ipconnect.de. [79.251.142.80])\r
+       by mx.google.com with ESMTPSA id dg7sm5297762wib.24.2014.12.10.00.13.50\r
+       for <multiple recipients>\r
+       (version=TLSv1.2 cipher=RC4-SHA bits=128/128);\r
+       Wed, 10 Dec 2014 00:13:51 -0800 (PST)\r
+Date: Wed, 10 Dec 2014 09:14:14 +0100\r
+From: Franz Fellner <alpine.art.de@gmail.com>\r
+To: Sebastian Fischmeister <sfischme@uwaterloo.ca>\r
+Message-ID: <548800d5ecc8b_551ca3e88c@TP_L520.notmuch>\r
+In-Reply-To: <87wq60e2q5.fsf@uwaterloo.ca>\r
+References: <87wq60e2q5.fsf@uwaterloo.ca>\r
+Subject: RE: email snoozing in notmuch\r
+Mime-Version: 1.0\r
+Content-Type: text/plain;\r
+ charset=utf-8\r
+Content-Transfer-Encoding: 7bit\r
+Attach: \r
+Cc: notmuch@notmuchmail.org\r
+X-BeenThere: notmuch@notmuchmail.org\r
+X-Mailman-Version: 2.1.13\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: Wed, 10 Dec 2014 08:13:58 -0000\r
+\r
+Hi,\r
+\r
+Sebastian Fischmeister wrote:\r
+> Hi,\r
+> \r
+> I'm thinking of how to realize the mail snoozing feature with notmuch,\r
+> so that certain emails won't become visible (in the search) until a\r
+> certain day/time (e.g., 10 days from now).\r
+> \r
+> Using the tag as an absolute date when the mail should become visible\r
+> again, tags should be searchable and interpretable as dates. The search\r
+> would then be something like: notmuch search tag-as-date < now and\r
+> tag:inbox\r
+\r
+It is not neccessary to make notmuch interpret tags as date - just interpret them yourself ;)\r
+You can easily run your own scripts and modify tags/mails. So a simple solution might be:\r
+* Add "snoozed" to your notmuch exclude_tags (see config file)\r
+* To snooze a mail run in your mail client "tag +snoozed +snoozeby-10-days"\r
+  or "tag +snoozed +snoozeuntil-2015-01-09"\r
+* Your script (e.g. run as cronjob or after notmuch new) now \r
+  - queries for "tag:snoozed"\r
+  - looks for snoozeuntil-* tag and parses the tag into a date. If date < now remove snooze-tags.\r
+  - looks for (relative) snoozeby tag and transform it into (absolute) snoozeuntil tag.\r
+(should be not too hard using e.g. the python or ruby bindings)\r
+\r
+Of course you can use an own email header to store the snoozeuntil value.\r
+With such a header it should be possible to use afew [1] for automated snooze-tag-management\r
+instead of a hand-crafted script.\r
+\r
+Regards\r
+Franz\r
+\r
+[1] https://github.com/teythoon/afew\r
+\r
+> \r
+> Using the receive date as base and encoding the delay as relative time\r
+> from that, would still need the ability to interpret tag values as\r
+> numbers:\r
+> \r
+> notmuch search date:01012011..15days and tag-as-number < 10 and tag:inbox\r
+> \r
+> Any ideas how the snoozing feature can be implemented with what is\r
+> already present in notmuch?\r
+> \r
+> Thanks,\r
+>   Sebastian\r
+> _______________________________________________\r
+> notmuch mailing list\r
+> notmuch@notmuchmail.org\r
+> http://notmuchmail.org/mailman/listinfo/notmuch\r
+\r
+\r