Re: Bug: problem decoding some non-ascii characters in subjects

diff --git a/84/fd91ebb1a0a19ff799a2f9d237fbbfe730c29f b/84/fd91ebb1a0a19ff799a2f9d237fbbfe730c29f
new file mode 100644 (file)
index 0000000..cf41f80
--- /dev/null
+++ b/84/fd91ebb1a0a19ff799a2f9d237fbbfe730c29f
@@ -0,0 +1,83 @@
+Return-Path: <jani@nikula.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 olra.theworths.org (Postfix) with ESMTP id A4E9440BC79\r
+       for <notmuch@notmuchmail.org>; Fri,  8 Feb 2013 03:22:02 -0800 (PST)\r
+X-Virus-Scanned: Debian amavisd-new at olra.theworths.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: -0.7\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=-0.7 tagged_above=-999 required=5\r
+       tests=[RCVD_IN_DNSWL_LOW=-0.7] 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 yMDxUCuqJZwT for <notmuch@notmuchmail.org>;\r
+       Fri,  8 Feb 2013 03:22:02 -0800 (PST)\r
+Received: from mail-bk0-f52.google.com (mail-bk0-f52.google.com\r
+       [209.85.214.52]) (using TLSv1 with cipher RC4-SHA (128/128 bits))\r
+       (No client certificate requested)\r
+       by olra.theworths.org (Postfix) with ESMTPS id 1633D4077F5\r
+       for <notmuch@notmuchmail.org>; Fri,  8 Feb 2013 03:22:01 -0800 (PST)\r
+Received: by mail-bk0-f52.google.com with SMTP id jk13so1575115bkc.25\r
+       for <notmuch@notmuchmail.org>; Fri, 08 Feb 2013 03:22:00 -0800 (PST)\r
+X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;\r
+       d=google.com; s=20120113;\r
+       h=x-received:from:to:subject:in-reply-to:references:user-agent:date\r
+       :message-id:mime-version:content-type:content-transfer-encoding\r
+       :x-gm-message-state;\r
+       bh=M+IToewtdCx2KLxlrQl2GTMR3hZQd1FE+nAfQTli2Ug=;\r
+       b=GWqkjFdYgR6bT/fOXK5ifcCWURxQBTu45qUIW4gVbTwsZE9JG82ugwmnWRwkktYS/1\r
+       F3sS1HSW7R3eXHNQ9BAMNmmwRnHrRrzNqX6+DKorHSVxaKbtpqHKfUNrfGezdRb9FTfW\r
+       3Pivbyx7dcHvsUiXuPs0cemBOWRMJ8CR7Z/RQcDuz2KOglutpvYxH+g5KwSKmBiasEEM\r
+       23l5ckks9ARbYEB+TCQV0SbRmguL6QH9xNIqIIK3b9T7pCsRAYB8LfaUKJhO+/suuc1i\r
+       vWcpk/6T5kynmWfYFsMpcB1SnT5f4DpoN9E1XmBsvEyTvL2Fb//hAOZNLQj4Bivheo6U\r
+       xtvA==\r
+X-Received: by 10.204.3.220 with SMTP id 28mr1338611bko.62.1360322519368;\r
+       Fri, 08 Feb 2013 03:21:59 -0800 (PST)\r
+Received: from localhost ([2001:4b98:dc0:43:216:3eff:fe1b:25f3])\r
+       by mx.google.com with ESMTPS id x18sm6001792bkw.4.2013.02.08.03.21.55\r
+       (version=TLSv1.1 cipher=RC4-SHA bits=128/128);\r
+       Fri, 08 Feb 2013 03:21:57 -0800 (PST)\r
+From: Jani Nikula <jani@nikula.org>\r
+To: Albin Stjerna <albin.stjerna@gmail.com>, notmuch@notmuchmail.org\r
+Subject: Re: Bug: problem decoding some non-ascii characters in subjects\r
+In-Reply-To: <87txpnds0k.fsf@hecate.student.uu.se>\r
+References: <87txpnds0k.fsf@hecate.student.uu.se>\r
+User-Agent: Notmuch/0.14+259~gdee88db (http://notmuchmail.org) Emacs/23.2.1\r
+       (x86_64-pc-linux-gnu)\r
+Date: Fri, 08 Feb 2013 12:21:47 +0100\r
+Message-ID: <8738x7kq44.fsf@nikula.org>\r
+MIME-Version: 1.0\r
+Content-Type: text/plain; charset=utf-8\r
+Content-Transfer-Encoding: quoted-printable\r
+X-Gm-Message-State:\r
+ ALoCoQl8VcaBQfimk0J/MWBcOiDEoQyGnOlODg8SyewkMgh9d61pRl5V/VGGWoippJcpceyOKN95\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: Fri, 08 Feb 2013 11:22:02 -0000\r
+\r
+On Fri, 08 Feb 2013, Albin Stjerna <albin.stjerna@gmail.com> wrote:\r
+> I've been noticing that notmuch has some problems decoding certain\r
+> strangely-encoded non-ascii characters in certain emails. For example,\r
+> today I got this: [BIBLIST] Digitaliseringensprojektens skadliga\r
+> f=3D?ISO-8859-1?Q?=3DF6rk=3DE4rlek_f=3DF6r_?=3D PDF-formatet (should be\r
+> rendered: =C2=BBDigitaliseringsprojektens skadliga f=C3=B6rk=C3=A4rlek f=\r
+=C3=B6r\r
+> PDF-formatet=C2=AB).\r
+>\r
+> Apparently, some metadata is passed on to help the MUA decode the\r
+> string, but notmuch doesn't seem to handle it. Entire emails can of\r
+> course be supplied as needed.\r
+\r
+Please copy paste the Subject: header directly from the message file.\r