From 4d25a68353ffe25b0e2defe2f7bac8dde25bd918 Mon Sep 17 00:00:00 2001 From: Jani Nikula Date: Sun, 10 Feb 2013 14:21:40 +0200 Subject: [PATCH] Re: Bug: problem decoding some non-ascii characters in subjects --- 24/9ed2e198408fee019daea68c64dfb10f11c3b9 | 94 +++++++++++++++++++++++ 1 file changed, 94 insertions(+) create mode 100644 24/9ed2e198408fee019daea68c64dfb10f11c3b9 diff --git a/24/9ed2e198408fee019daea68c64dfb10f11c3b9 b/24/9ed2e198408fee019daea68c64dfb10f11c3b9 new file mode 100644 index 000000000..d5e74c98f --- /dev/null +++ b/24/9ed2e198408fee019daea68c64dfb10f11c3b9 @@ -0,0 +1,94 @@ +Return-Path: +X-Original-To: notmuch@notmuchmail.org +Delivered-To: notmuch@notmuchmail.org +Received: from localhost (localhost [127.0.0.1]) + by olra.theworths.org (Postfix) with ESMTP id 8D490431FAF + for ; Sun, 10 Feb 2013 19:52:34 -0800 (PST) +X-Virus-Scanned: Debian amavisd-new at olra.theworths.org +X-Spam-Flag: NO +X-Spam-Score: -0.7 +X-Spam-Level: +X-Spam-Status: No, score=-0.7 tagged_above=-999 required=5 + tests=[RCVD_IN_DNSWL_LOW=-0.7] 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 FYQZkutsh7v0 for ; + Sun, 10 Feb 2013 19:52:34 -0800 (PST) +Received: from mail-la0-f46.google.com (mail-la0-f46.google.com + [209.85.215.46]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) + (No client certificate requested) + by olra.theworths.org (Postfix) with ESMTPS id DD218431FAE + for ; Sun, 10 Feb 2013 19:52:33 -0800 (PST) +Received: by mail-la0-f46.google.com with SMTP id fq12so5423730lab.19 + for ; Sun, 10 Feb 2013 19:52:30 -0800 (PST) +X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; + d=google.com; s=20120113; + h=x-received:from:to:subject:in-reply-to:references:user-agent:date + :message-id:mime-version:content-type:x-gm-message-state; + bh=5hf7EFKHEC+oDicKc1Da0ya808tcwv0gGu64sxTWvlQ=; + b=NelZl+OoNGdWHdPU9lEckPnMnsvrKBUOle8CmwQweW9Ybhk2nnCCQao4UV7xuAGY8V + vWJaDJ71Kp4IxfAWF6y5KIPxkppjHOMrfgwk8z0K8gPjjWZigXsVnJ63ov97boglpvWz + 16RFXVOW2XJVi11siXSKnzXsTKYQHUxXNwdmMVCf2ii91gsbREhnoo6K40h2xLJfxuiw + FAGNFnhQk3Ssds0oEcbaGeOR+oQp/go1k8xzu2zk1wDQ3XBthoyrE3MaOyjHjomki40T + iB0/6vmrEv6wVLi1FPDdJyfWwyVOWCMi6KjYIkB/N6qiPRzPFFzmXAE3Lf+aVRoLIVbr + CmVA== +X-Received: by 10.152.102.177 with SMTP id fp17mr10070304lab.0.1360498898108; + Sun, 10 Feb 2013 04:21:38 -0800 (PST) +Received: from localhost (dsl-hkibrasgw4-50df51-27.dhcp.inet.fi. + [80.223.81.27]) + by mx.google.com with ESMTPS id ie3sm20002773lab.4.2013.02.10.04.21.36 + (version=TLSv1.2 cipher=RC4-SHA bits=128/128); + Sun, 10 Feb 2013 04:21:36 -0800 (PST) +From: Jani Nikula +To: Albin Stjerna , notmuch@notmuchmail.org +Subject: Re: Bug: problem decoding some non-ascii characters in subjects +In-Reply-To: <87liawefk3.fsf@hecate.student.uu.se> +References: <87txpnds0k.fsf@hecate.student.uu.se> <8738x7kq44.fsf@nikula.org> + <87pq09eu41.fsf@hecate.student.uu.se> <87mwvd6bst.fsf@nikula.org> + <87liawefk3.fsf@hecate.student.uu.se> +User-Agent: Notmuch/0.14+255~gff3cc55 (http://notmuchmail.org) Emacs/24.2.1 + (x86_64-pc-linux-gnu) +Date: Sun, 10 Feb 2013 14:21:40 +0200 +Message-ID: <87k3qg5pgr.fsf@nikula.org> +MIME-Version: 1.0 +Content-Type: text/plain +X-Gm-Message-State: + ALoCoQkBGppypAHHmxVEM81vjbwaRfk7bomqyrPN+5ghiH2yaAhQiikhviuLogch3kD2zmH3MpeD +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: Mon, 11 Feb 2013 03:52:34 -0000 + +On Sun, 10 Feb 2013, Albin Stjerna wrote: +> Hm. So I should report this to Thunderbird? I tried searching through +> their bug reports but didn't find anything. + +I tried that too; there were other RFC 2047 related header bugs but +could not find this one. And the other bugs were old and fixed. Judging +by the User-Agent header this is fairly up-to-date Thunderbird. + +It seems to be list mail. It would not surprise me that some ill-advised +mailing list manager would decode and re-encode the subject. One could +try sending the same message directly and through the list, and see if +there's a difference. + +> I didn't think it was a bug, since Gmail rendered it just fine. + +It's possible they interpret the RFC in a more relaxed way. AFAICS +notmuch relies on gmime to handle this, so I think we would have to go +out of our way to work around this in notmuch. A quick search did not +bring up anything gmime related about this, so I don't know if this has +been discussed in the gime context. + + +BR, +Jani. -- 2.26.2