Re: [PATCH] test: Add test for searching of uncommonly encoded messages
authorSerge Z <triumhiz@yandex.ru>
Sat, 25 Feb 2012 08:36:00 +0000 (12:36 +0400)
committerW. Trevor King <wking@tremily.us>
Fri, 7 Nov 2014 17:44:57 +0000 (09:44 -0800)
2d/6e8ba933df189d80426f244f9ddf02a603b885 [new file with mode: 0644]

diff --git a/2d/6e8ba933df189d80426f244f9ddf02a603b885 b/2d/6e8ba933df189d80426f244f9ddf02a603b885
new file mode 100644 (file)
index 0000000..36fd5d9
--- /dev/null
@@ -0,0 +1,93 @@
+Return-Path: <triumhiz@yandex.ru>\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 9D4C4429E3B\r
+       for <notmuch@notmuchmail.org>; Sat, 25 Feb 2012 19:05:38 -0800 (PST)\r
+X-Virus-Scanned: Debian amavisd-new at olra.theworths.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: -0.1\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=-0.1 tagged_above=-999 required=5\r
+       tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1,\r
+       RCVD_IN_DNSWL_NONE=-0.0001] 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 l67f0-amr7PI for <notmuch@notmuchmail.org>;\r
+       Sat, 25 Feb 2012 19:05:36 -0800 (PST)\r
+Received: from forward17.mail.yandex.net (forward17.mail.yandex.net\r
+       [95.108.253.142])\r
+       by olra.theworths.org (Postfix) with ESMTP id 35D5A41644C\r
+       for <notmuch@notmuchmail.org>; Sat, 25 Feb 2012 18:46:06 -0800 (PST)\r
+Received: from smtp18.mail.yandex.net (smtp18.mail.yandex.net [95.108.252.18])\r
+       by forward17.mail.yandex.net (Yandex) with ESMTP id A8C9E10619DE\r
+       for <notmuch@notmuchmail.org>; Sat, 25 Feb 2012 12:33:09 +0400 (MSK)\r
+DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail;\r
+       t=1330158789; bh=GV7QPHI4H1bDQs3sWn7hzTqHWl/d11xrJxQUcDyI7+4=;\r
+       h=Content-Type:MIME-Version:Content-Transfer-Encoding:From:To:\r
+       References:In-Reply-To:Message-ID:Subject:Date;\r
+       b=wT0GZcQkr06uW+xDwYgRG/4XM7i0AnUI0bJpdOV7QNiw3hB6uJ/DwAYJYnmCaaC9m\r
+       CpcXfUIlPJiT2ZEIb5ApqU+mUaNbiLHLnOMPVnnxyX0At6kFfCFooZD5BeW1V32iH7\r
+       AlDMpD1eSalzyupq7yw0oOgpIxjawQDBgfxgO7X4=\r
+Received: from smtp18.mail.yandex.net (localhost [127.0.0.1])\r
+       by smtp18.mail.yandex.net (Yandex) with ESMTP id 650BC18A0143\r
+       for <notmuch@notmuchmail.org>; Sat, 25 Feb 2012 12:33:09 +0400 (MSK)\r
+DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail;\r
+       t=1330158789; bh=GV7QPHI4H1bDQs3sWn7hzTqHWl/d11xrJxQUcDyI7+4=;\r
+       h=Content-Type:MIME-Version:Content-Transfer-Encoding:From:To:\r
+       References:In-Reply-To:Message-ID:Subject:Date;\r
+       b=wT0GZcQkr06uW+xDwYgRG/4XM7i0AnUI0bJpdOV7QNiw3hB6uJ/DwAYJYnmCaaC9m\r
+       CpcXfUIlPJiT2ZEIb5ApqU+mUaNbiLHLnOMPVnnxyX0At6kFfCFooZD5BeW1V32iH7\r
+       AlDMpD1eSalzyupq7yw0oOgpIxjawQDBgfxgO7X4=\r
+Received: from host-136-152-66-217.spbmts.ru (host-136-152-66-217.spbmts.ru\r
+       [217.66.152.136])\r
+       by smtp18.mail.yandex.net (nwsmtp/Yandex) with ESMTP id\r
+       X7m4snL6-X8mqNomh; Sat, 25 Feb 2012 12:33:08 +0400\r
+X-Yandex-Spam: 1\r
+Content-Type: text/plain; charset="utf-8"\r
+MIME-Version: 1.0\r
+Content-Transfer-Encoding: quoted-printable\r
+From: Serge Z <triumhiz@yandex.ru>\r
+User-Agent: alot/0.21+\r
+To: notmuch@notmuchmail.org\r
+References: <877gzd5axk.fsf@steelpick.2x.cz>\r
+       <1330043595-22054-1-git-send-email-sojkam1@fel.cvut.cz>\r
+       <20120224042925.2870.87924@localhost> <874nug67il.fsf@steelpick.2x.cz>\r
+       <20120224075700.13214.28221@localhost> <874nugiq2g.fsf@steelpick.2x.cz>\r
+In-Reply-To: <874nugiq2g.fsf@steelpick.2x.cz>\r
+Message-ID: <20120225083600.17873.66388@localhost>\r
+Subject: Re: [PATCH] test: Add test for searching of uncommonly encoded\r
+       messages\r
+Date: Sat, 25 Feb 2012 12:36:00 +0400\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: Sun, 26 Feb 2012 03:05:39 -0000\r
+\r
+\r
+Hi!\r
+I've struck another problem:\r
+\r
+I've got an html/text email with body encoded with cp1251.\r
+Its encoding is mentioned in both Content-type: email header and html <meta>\r
+tag. So when the client tries to display it with external html2text convert=\r
+er,\r
+The message is decoded twice: first by client, second by html2text (I use w=\r
+3m).\r
+\r
+As I understand, notmuch (while indexing this message) decodes it once and\r
+index it in the right way (though including html tags to index). But what if\r
+the message contains no "charset" option in Content-Type email header but\r
+contain <meta> content-type tag with charset noted? Should such message be\r
+considered as being composed wrong or it should be indexed with diving into\r
+html details (content-type)?\r
+\r