1 Return-Path: <jani@nikula.org>
\r
2 X-Original-To: notmuch@notmuchmail.org
\r
3 Delivered-To: notmuch@notmuchmail.org
\r
4 Received: from localhost (localhost [127.0.0.1])
\r
5 by olra.theworths.org (Postfix) with ESMTP id 8D490431FAF
\r
6 for <notmuch@notmuchmail.org>; Sun, 10 Feb 2013 19:52:34 -0800 (PST)
\r
7 X-Virus-Scanned: Debian amavisd-new at olra.theworths.org
\r
11 X-Spam-Status: No, score=-0.7 tagged_above=-999 required=5
\r
12 tests=[RCVD_IN_DNSWL_LOW=-0.7] autolearn=disabled
\r
13 Received: from olra.theworths.org ([127.0.0.1])
\r
14 by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)
\r
15 with ESMTP id FYQZkutsh7v0 for <notmuch@notmuchmail.org>;
\r
16 Sun, 10 Feb 2013 19:52:34 -0800 (PST)
\r
17 Received: from mail-la0-f46.google.com (mail-la0-f46.google.com
\r
18 [209.85.215.46]) (using TLSv1 with cipher RC4-SHA (128/128 bits))
\r
19 (No client certificate requested)
\r
20 by olra.theworths.org (Postfix) with ESMTPS id DD218431FAE
\r
21 for <notmuch@notmuchmail.org>; Sun, 10 Feb 2013 19:52:33 -0800 (PST)
\r
22 Received: by mail-la0-f46.google.com with SMTP id fq12so5423730lab.19
\r
23 for <notmuch@notmuchmail.org>; Sun, 10 Feb 2013 19:52:30 -0800 (PST)
\r
24 X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
\r
25 d=google.com; s=20120113;
\r
26 h=x-received:from:to:subject:in-reply-to:references:user-agent:date
\r
27 :message-id:mime-version:content-type:x-gm-message-state;
\r
28 bh=5hf7EFKHEC+oDicKc1Da0ya808tcwv0gGu64sxTWvlQ=;
\r
29 b=NelZl+OoNGdWHdPU9lEckPnMnsvrKBUOle8CmwQweW9Ybhk2nnCCQao4UV7xuAGY8V
\r
30 vWJaDJ71Kp4IxfAWF6y5KIPxkppjHOMrfgwk8z0K8gPjjWZigXsVnJ63ov97boglpvWz
\r
31 16RFXVOW2XJVi11siXSKnzXsTKYQHUxXNwdmMVCf2ii91gsbREhnoo6K40h2xLJfxuiw
\r
32 FAGNFnhQk3Ssds0oEcbaGeOR+oQp/go1k8xzu2zk1wDQ3XBthoyrE3MaOyjHjomki40T
\r
33 iB0/6vmrEv6wVLi1FPDdJyfWwyVOWCMi6KjYIkB/N6qiPRzPFFzmXAE3Lf+aVRoLIVbr
\r
35 X-Received: by 10.152.102.177 with SMTP id fp17mr10070304lab.0.1360498898108;
\r
36 Sun, 10 Feb 2013 04:21:38 -0800 (PST)
\r
37 Received: from localhost (dsl-hkibrasgw4-50df51-27.dhcp.inet.fi.
\r
39 by mx.google.com with ESMTPS id ie3sm20002773lab.4.2013.02.10.04.21.36
\r
40 (version=TLSv1.2 cipher=RC4-SHA bits=128/128);
\r
41 Sun, 10 Feb 2013 04:21:36 -0800 (PST)
\r
42 From: Jani Nikula <jani@nikula.org>
\r
43 To: Albin Stjerna <albin.stjerna@gmail.com>, notmuch@notmuchmail.org
\r
44 Subject: Re: Bug: problem decoding some non-ascii characters in subjects
\r
45 In-Reply-To: <87liawefk3.fsf@hecate.student.uu.se>
\r
46 References: <87txpnds0k.fsf@hecate.student.uu.se> <8738x7kq44.fsf@nikula.org>
\r
47 <87pq09eu41.fsf@hecate.student.uu.se> <87mwvd6bst.fsf@nikula.org>
\r
48 <87liawefk3.fsf@hecate.student.uu.se>
\r
49 User-Agent: Notmuch/0.14+255~gff3cc55 (http://notmuchmail.org) Emacs/24.2.1
\r
50 (x86_64-pc-linux-gnu)
\r
51 Date: Sun, 10 Feb 2013 14:21:40 +0200
\r
52 Message-ID: <87k3qg5pgr.fsf@nikula.org>
\r
54 Content-Type: text/plain
\r
56 ALoCoQkBGppypAHHmxVEM81vjbwaRfk7bomqyrPN+5ghiH2yaAhQiikhviuLogch3kD2zmH3MpeD
\r
57 X-BeenThere: notmuch@notmuchmail.org
\r
58 X-Mailman-Version: 2.1.13
\r
60 List-Id: "Use and development of the notmuch mail system."
\r
61 <notmuch.notmuchmail.org>
\r
62 List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,
\r
63 <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>
\r
64 List-Archive: <http://notmuchmail.org/pipermail/notmuch>
\r
65 List-Post: <mailto:notmuch@notmuchmail.org>
\r
66 List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>
\r
67 List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,
\r
68 <mailto:notmuch-request@notmuchmail.org?subject=subscribe>
\r
69 X-List-Received-Date: Mon, 11 Feb 2013 03:52:34 -0000
\r
71 On Sun, 10 Feb 2013, Albin Stjerna <albin.stjerna@gmail.com> wrote:
\r
72 > Hm. So I should report this to Thunderbird? I tried searching through
\r
73 > their bug reports but didn't find anything.
\r
75 I tried that too; there were other RFC 2047 related header bugs but
\r
76 could not find this one. And the other bugs were old and fixed. Judging
\r
77 by the User-Agent header this is fairly up-to-date Thunderbird.
\r
79 It seems to be list mail. It would not surprise me that some ill-advised
\r
80 mailing list manager would decode and re-encode the subject. One could
\r
81 try sending the same message directly and through the list, and see if
\r
82 there's a difference.
\r
84 > I didn't think it was a bug, since Gmail rendered it just fine.
\r
86 It's possible they interpret the RFC in a more relaxed way. AFAICS
\r
87 notmuch relies on gmime to handle this, so I think we would have to go
\r
88 out of our way to work around this in notmuch. A quick search did not
\r
89 bring up anything gmime related about this, so I don't know if this has
\r
90 been discussed in the gime context.
\r