From 831a6dc49ea1b11a0a542d7584fdc8fc29c174a0 Mon Sep 17 00:00:00 2001 From: "J. Lewis Muir" Date: Sat, 18 Jul 2015 10:48:57 +1900 Subject: [PATCH] Re: Searching for phrases in the body of an email --- 01/71628364aaba026cca6d3a1692cac1e0b7730d | 85 +++++++++++++++++++++++ 1 file changed, 85 insertions(+) create mode 100644 01/71628364aaba026cca6d3a1692cac1e0b7730d diff --git a/01/71628364aaba026cca6d3a1692cac1e0b7730d b/01/71628364aaba026cca6d3a1692cac1e0b7730d new file mode 100644 index 000000000..f2b10d691 --- /dev/null +++ b/01/71628364aaba026cca6d3a1692cac1e0b7730d @@ -0,0 +1,85 @@ +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 BB5656DE1778 + for ; Fri, 17 Jul 2015 08:49:02 -0700 (PDT) +X-Virus-Scanned: Debian amavisd-new at cworth.org +X-Spam-Flag: NO +X-Spam-Score: 0.219 +X-Spam-Level: +X-Spam-Status: No, score=0.219 tagged_above=-999 required=5 tests=[AWL=0.219] + 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 fEeW4ClsC0xR for ; + Fri, 17 Jul 2015 08:49:00 -0700 (PDT) +Received: from tuna.imca.aps.anl.gov (tuna.imca.aps.anl.gov [164.54.200.33]) + by arlo.cworth.org (Postfix) with ESMTP id 8D9846DE1761 + for ; Fri, 17 Jul 2015 08:49:00 -0700 (PDT) +Received: from mink.imca.aps.anl.gov (seal.imca.aps.anl.gov [164.54.200.39]) + by tuna.imca.aps.anl.gov (Postfix) with ESMTP id F34462005F + for ; Fri, 17 Jul 2015 10:48:55 -0500 (CDT) +Message-ID: <55A923E9.5070509@imca-cat.org> +Date: Fri, 17 Jul 2015 10:48:57 -0500 +From: "J. Lewis Muir" +MIME-Version: 1.0 +To: Notmuch list +Subject: Re: Searching for phrases in the body of an email +References: <20150717121111.GF25651@chitra.no-ip.org> +In-Reply-To: <20150717121111.GF25651@chitra.no-ip.org> +Content-Type: text/plain; charset=utf-8 +Content-Transfer-Encoding: 7bit +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: Fri, 17 Jul 2015 15:49:02 -0000 + +On 7/17/15 7:11 AM, Suvayu Ali wrote: +> Hi, +> +> I'm trying to find those annoying emails which have useless plain +> text parts. As I recall, they had a phrase something along the lines +> of "not available in plain text" or "no plain text". So of course I +> searched for "plain text". But that returns hundreds of messages with +> no obvious matches, I can't even find the phrase "plain text" in the +> body for most of the results! + +[snip] + +> I do not understand this at all! Any thoughts? + +Hello, Suvayu. + +I can't speak to the notmuch search results since I actually don't have +experience with it (I'm planning to switch my email setup to using +notmuch, but I actually haven't switched yet!), but I can give a few +ideas for some of your puzzlements: + +1. Perhaps you are remembering the "no plain text" message incorrectly? + For example, the message could have referred to "text/plain" or + "plaintext" (no space). These would be sufficiently different to not + match your grep pattern. + +2. Perhaps your email client rendered the "no plain text" message when + it encountered an email with only a "text/html" content type? In + this case, the "no plain text" (or whatever) message would not be + present in the email itself since it would be generated by the email + client when rendering the email. + +3. A really long shot, but could a line wrap have occurred after "plain" + such that "text" appeared on the next line? Your grep pattern would + not match that. + +Regards, + +Lewis -- 2.26.2