Re: Searching for phrases in the body of an email

diff --git a/01/71628364aaba026cca6d3a1692cac1e0b7730d b/01/71628364aaba026cca6d3a1692cac1e0b7730d
new file mode 100644 (file)
index 0000000..f2b10d6
--- /dev/null
+++ b/01/71628364aaba026cca6d3a1692cac1e0b7730d
@@ -0,0 +1,85 @@
+Return-Path: <jlmuir@imca-cat.org>\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 BB5656DE1778\r
+ for <notmuch@notmuchmail.org>; Fri, 17 Jul 2015 08:49:02 -0700 (PDT)\r
+X-Virus-Scanned: Debian amavisd-new at cworth.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: 0.219\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=0.219 tagged_above=-999 required=5 tests=[AWL=0.219]\r
+ 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 fEeW4ClsC0xR for <notmuch@notmuchmail.org>;\r
+ Fri, 17 Jul 2015 08:49:00 -0700 (PDT)\r
+Received: from tuna.imca.aps.anl.gov (tuna.imca.aps.anl.gov [164.54.200.33])\r
+ by arlo.cworth.org (Postfix) with ESMTP id 8D9846DE1761\r
+ for <notmuch@notmuchmail.org>; Fri, 17 Jul 2015 08:49:00 -0700 (PDT)\r
+Received: from mink.imca.aps.anl.gov (seal.imca.aps.anl.gov [164.54.200.39])\r
+ by tuna.imca.aps.anl.gov (Postfix) with ESMTP id F34462005F\r
+ for <notmuch@notmuchmail.org>; Fri, 17 Jul 2015 10:48:55 -0500 (CDT)\r
+Message-ID: <55A923E9.5070509@imca-cat.org>\r
+Date: Fri, 17 Jul 2015 10:48:57 -0500\r
+From: "J. Lewis Muir" <jlmuir@imca-cat.org>\r
+MIME-Version: 1.0\r
+To: Notmuch list <notmuch@notmuchmail.org>\r
+Subject: Re: Searching for phrases in the body of an email\r
+References: <20150717121111.GF25651@chitra.no-ip.org>\r
+In-Reply-To: <20150717121111.GF25651@chitra.no-ip.org>\r
+Content-Type: text/plain; charset=utf-8\r
+Content-Transfer-Encoding: 7bit\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: Fri, 17 Jul 2015 15:49:02 -0000\r
+\r
+On 7/17/15 7:11 AM, Suvayu Ali wrote:\r
+> Hi,\r
+>\r
+> I'm trying to find those annoying emails which have useless plain\r
+> text parts.  As I recall, they had a phrase something along the lines\r
+> of "not available in plain text" or "no plain text".  So of course I\r
+> searched for "plain text".  But that returns hundreds of messages with\r
+> no obvious matches, I can't even find the phrase "plain text" in the\r
+> body for most of the results!\r
+\r
+[snip]\r
+\r
+> I do not understand this at all!  Any thoughts?\r
+\r
+Hello, Suvayu.\r
+\r
+I can't speak to the notmuch search results since I actually don't have\r
+experience with it (I'm planning to switch my email setup to using\r
+notmuch, but I actually haven't switched yet!), but I can give a few\r
+ideas for some of your puzzlements:\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
+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
+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
+Regards,\r
+\r
+Lewis\r