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