Re: Bug: problem decoding some non-ascii characters in subjects
authorJani Nikula <jani@nikula.org>
Sun, 10 Feb 2013 12:21:40 +0000 (14:21 +0200)
committerW. Trevor King <wking@tremily.us>
Fri, 7 Nov 2014 17:53:32 +0000 (09:53 -0800)
24/9ed2e198408fee019daea68c64dfb10f11c3b9 [new file with mode: 0644]

diff --git a/24/9ed2e198408fee019daea68c64dfb10f11c3b9 b/24/9ed2e198408fee019daea68c64dfb10f11c3b9
new file mode 100644 (file)
index 0000000..d5e74c9
--- /dev/null
@@ -0,0 +1,94 @@
+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 8D490431FAF\r
+       for <notmuch@notmuchmail.org>; Sun, 10 Feb 2013 19:52:34 -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 FYQZkutsh7v0 for <notmuch@notmuchmail.org>;\r
+       Sun, 10 Feb 2013 19:52:34 -0800 (PST)\r
+Received: from mail-la0-f46.google.com (mail-la0-f46.google.com\r
+       [209.85.215.46]) (using TLSv1 with cipher RC4-SHA (128/128 bits))\r
+       (No client certificate requested)\r
+       by olra.theworths.org (Postfix) with ESMTPS id DD218431FAE\r
+       for <notmuch@notmuchmail.org>; Sun, 10 Feb 2013 19:52:33 -0800 (PST)\r
+Received: by mail-la0-f46.google.com with SMTP id fq12so5423730lab.19\r
+       for <notmuch@notmuchmail.org>; Sun, 10 Feb 2013 19:52:30 -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:x-gm-message-state;\r
+       bh=5hf7EFKHEC+oDicKc1Da0ya808tcwv0gGu64sxTWvlQ=;\r
+       b=NelZl+OoNGdWHdPU9lEckPnMnsvrKBUOle8CmwQweW9Ybhk2nnCCQao4UV7xuAGY8V\r
+       vWJaDJ71Kp4IxfAWF6y5KIPxkppjHOMrfgwk8z0K8gPjjWZigXsVnJ63ov97boglpvWz\r
+       16RFXVOW2XJVi11siXSKnzXsTKYQHUxXNwdmMVCf2ii91gsbREhnoo6K40h2xLJfxuiw\r
+       FAGNFnhQk3Ssds0oEcbaGeOR+oQp/go1k8xzu2zk1wDQ3XBthoyrE3MaOyjHjomki40T\r
+       iB0/6vmrEv6wVLi1FPDdJyfWwyVOWCMi6KjYIkB/N6qiPRzPFFzmXAE3Lf+aVRoLIVbr\r
+       CmVA==\r
+X-Received: by 10.152.102.177 with SMTP id fp17mr10070304lab.0.1360498898108; \r
+       Sun, 10 Feb 2013 04:21:38 -0800 (PST)\r
+Received: from localhost (dsl-hkibrasgw4-50df51-27.dhcp.inet.fi.\r
+       [80.223.81.27])\r
+       by mx.google.com with ESMTPS id ie3sm20002773lab.4.2013.02.10.04.21.36\r
+       (version=TLSv1.2 cipher=RC4-SHA bits=128/128);\r
+       Sun, 10 Feb 2013 04:21:36 -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: <87liawefk3.fsf@hecate.student.uu.se>\r
+References: <87txpnds0k.fsf@hecate.student.uu.se> <8738x7kq44.fsf@nikula.org>\r
+       <87pq09eu41.fsf@hecate.student.uu.se> <87mwvd6bst.fsf@nikula.org>\r
+       <87liawefk3.fsf@hecate.student.uu.se>\r
+User-Agent: Notmuch/0.14+255~gff3cc55 (http://notmuchmail.org) Emacs/24.2.1\r
+       (x86_64-pc-linux-gnu)\r
+Date: Sun, 10 Feb 2013 14:21:40 +0200\r
+Message-ID: <87k3qg5pgr.fsf@nikula.org>\r
+MIME-Version: 1.0\r
+Content-Type: text/plain\r
+X-Gm-Message-State:\r
+ ALoCoQkBGppypAHHmxVEM81vjbwaRfk7bomqyrPN+5ghiH2yaAhQiikhviuLogch3kD2zmH3MpeD\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: Mon, 11 Feb 2013 03:52:34 -0000\r
+\r
+On Sun, 10 Feb 2013, Albin Stjerna <albin.stjerna@gmail.com> wrote:\r
+> Hm. So I should report this to Thunderbird? I tried searching through\r
+> their bug reports but didn't find anything.\r
+\r
+I tried that too; there were other RFC 2047 related header bugs but\r
+could not find this one. And the other bugs were old and fixed. Judging\r
+by the User-Agent header this is fairly up-to-date Thunderbird.\r
+\r
+It seems to be list mail. It would not surprise me that some ill-advised\r
+mailing list manager would decode and re-encode the subject. One could\r
+try sending the same message directly and through the list, and see if\r
+there's a difference.\r
+\r
+> I didn't think it was a bug, since Gmail rendered it just fine.\r
+\r
+It's possible they interpret the RFC in a more relaxed way. AFAICS\r
+notmuch relies on gmime to handle this, so I think we would have to go\r
+out of our way to work around this in notmuch. A quick search did not\r
+bring up anything gmime related about this, so I don't know if this has\r
+been discussed in the gime context.\r
+\r
+\r
+BR,\r
+Jani.\r