Re: Searching for phrases in the body of an email

diff --git a/0a/50abdc4e5e244f5de7272e6f12e0555a10850c b/0a/50abdc4e5e244f5de7272e6f12e0555a10850c
new file mode 100644 (file)
index 0000000..37a95d3
--- /dev/null
+++ b/0a/50abdc4e5e244f5de7272e6f12e0555a10850c
@@ -0,0 +1,110 @@
+Return-Path: <fatkasuvayu+linux@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 arlo.cworth.org (Postfix) with ESMTP id E6EC46DE0924\r
+ for <notmuch@notmuchmail.org>; Sat, 18 Jul 2015 02:11:45 -0700 (PDT)\r
+X-Virus-Scanned: Debian amavisd-new at cworth.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: -0.719\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=-0.719 tagged_above=-999 required=5 tests=[AWL=0.101,\r
+  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001,\r
+ RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01,\r
+ SPF_PASS=-0.001] 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 oGMlil-czEyr for <notmuch@notmuchmail.org>;\r
+ Sat, 18 Jul 2015 02:11:44 -0700 (PDT)\r
+Received: from mail-wi0-f170.google.com (mail-wi0-f170.google.com\r
+ [209.85.212.170])\r
+ by arlo.cworth.org (Postfix) with ESMTPS id BC8C26DE0352\r
+ for <notmuch@notmuchmail.org>; Sat, 18 Jul 2015 02:11:43 -0700 (PDT)\r
+Received: by widjy10 with SMTP id jy10so57364541wid.1\r
+ for <notmuch@notmuchmail.org>; Sat, 18 Jul 2015 02:11:41 -0700 (PDT)\r
+DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;\r
+ h=sender:date:from:to:subject:message-id:mail-followup-to:references\r
+ :mime-version:content-type:content-disposition:in-reply-to\r
+ :user-agent; bh=Lr6RFOEnf3Nfj985VwhUat0pxm9i34hMr+vBtAZY/Yg=;\r
+ b=iF2xBOES2Q9Vg9F2Ri7ykN+tWLjAWI39E+l3bhiWq0mZbXtJCkwzVAPLvNUsydOXBI\r
+ YmVPkKhm3sE5qwQziuTN9IHBYtR1R1grIUTTrfpzBdUnhNvH/gWIGqTlZEfBTvaYO+NF\r
+ Oo0pdFrqYiC9hsKQU89J5cARAI066qNgYWEC+cvd1LNqIPPiO/Y8XrBoaaheD6PElbWN\r
+ kMUolfXausfZUFxTwq/yGB8Tai5D4HEw8WT3MxPX7/IBMn29RL1I6iQn7+uMK0ne8P+s\r
+ yv+0AUqpSw2os8G2R+yBk8Z6qvEY9+xLLaUNWPon5ktPB3mp581r5OnxR0tMhWZa+eHG\r
+ IcmQ==\r
+X-Received: by 10.194.178.1 with SMTP id cu1mr37842626wjc.59.1437210701678;\r
+ Sat, 18 Jul 2015 02:11:41 -0700 (PDT)\r
+Received: from chitra.no-ip.org (ip82-139-115-46.lijbrandt.net.\r
+ [82.139.115.46])\r
+ by smtp.gmail.com with ESMTPSA id ju2sm1648603wid.12.2015.07.18.02.11.40\r
+ for <notmuch@notmuchmail.org>\r
+ (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);\r
+ Sat, 18 Jul 2015 02:11:41 -0700 (PDT)\r
+Sender: Suvayu Ali <fatkasuvayu@gmail.com>\r
+Date: Sat, 18 Jul 2015 11:11:39 +0200\r
+From: Suvayu Ali <fatkasuvayu+linux@gmail.com>\r
+To: notmuch@notmuchmail.org\r
+Subject: Re: Searching for phrases in the body of an email\r
+Message-ID: <20150718091139.GB8311@chitra.no-ip.org>\r
+Mail-Followup-To: notmuch@notmuchmail.org\r
+References: <20150717121111.GF25651@chitra.no-ip.org>\r
+ <55A923E9.5070509@imca-cat.org>\r
+MIME-Version: 1.0\r
+Content-Type: text/plain; charset=us-ascii\r
+Content-Disposition: inline\r
+In-Reply-To: <55A923E9.5070509@imca-cat.org>\r
+User-Agent: Mutt/1.5.23.1 (2014-03-12)\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: Sat, 18 Jul 2015 09:11:46 -0000\r
+\r
+Hi Lewis,\r
+\r
+On Fri, Jul 17, 2015 at 10:48:57AM -0500, J. Lewis Muir wrote:\r
+> \r
+> 1. Perhaps you are remembering the "no plain text" message incorrectly?\r
+>    For example, the message could have referred to "text/plain" or\r
+>    "plaintext" (no space).  These would be sufficiently different to not\r
+>    match your grep pattern.\r
+\r
+True, but my puzzlement is notmuch shouldn't return those results in the\r
+first place, since I provided a quoted string: "plain text", unless of\r
+course I need to escape the quotes.  Okay, just checked it, doesn't make\r
+a difference in the number of hits from notmuch.\r
+\r
+> 2. Perhaps your email client rendered the "no plain text" message when\r
+>    it encountered an email with only a "text/html" content type?  In\r
+>    this case, the "no plain text" (or whatever) message would not be\r
+>    present in the email itself since it would be generated by the email\r
+>    client when rendering the email.\r
+\r
+This is possible, but I use mutt.  As far as I know, it doesn't do\r
+"smart" things like that.  I also recall looking at the mime parts\r
+individually as I was surprised at the behaviour, and it was indeed a\r
+useless text/plain part with that message.\r
+\r
+> 3. A really long shot, but could a line wrap have occurred after "plain"\r
+>    such that "text" appeared on the next line?  Your grep pattern would\r
+>    not match that.\r
+\r
+Good point, I tried grepping for this instead: 'plain[[:space:]/]+text',\r
+no luck.\r
+\r
+Thanks for your comments.\r
+\r
+Cheers,\r
+\r
+-- \r
+Suvayu\r
+\r
+Open source is the future. It sets us free.\r