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 505FE41DB89
\r
6 for <notmuch@notmuchmail.org>; Sat, 9 Feb 2013 02:07:07 -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 l+RMh3JqqUg7 for <notmuch@notmuchmail.org>;
\r
16 Sat, 9 Feb 2013 02:07:06 -0800 (PST)
\r
17 Received: from mail-la0-f50.google.com (mail-la0-f50.google.com
\r
18 [209.85.215.50]) (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 9F90D41DB87
\r
21 for <notmuch@notmuchmail.org>; Sat, 9 Feb 2013 02:07:06 -0800 (PST)
\r
22 Received: by mail-la0-f50.google.com with SMTP id ec20so4547478lab.37
\r
23 for <notmuch@notmuchmail.org>; Sat, 09 Feb 2013 02:07:02 -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:content-transfer-encoding
\r
28 :x-gm-message-state;
\r
29 bh=2d0FKD0rsAQ8iqqV2C5twH6GTC22+64v7UDR+DhtGtA=;
\r
30 b=L/b2u/ye4I4BsMjk1l8R4uFeV7/ilobkJPUED/x1Mpt01xx/JfgbAlFNEPzUo2W03V
\r
31 lgxtnYIUwhvWSxDXZXF+by2ee/UE+kKAvUmer0mGVW3vE+Q5EGwqWJ92lLyvSTJ1JhYA
\r
32 hT+Ydx7bO00ICmN51WRhknBdgTE0UnQLTGv7Ao11K5FDdKinKy697YBcGR3xv/nE3ta3
\r
33 Amgsd0yMMFaa8+c4OCEONWnJOWIzAT11lYmtlbgvVzYewq+N4RYipUO/8TejDn2MgKQz
\r
34 mZMUBPJKLnyUXWCmYzxnTHlJeo9Gi80gurRUpGwXCexixBv5DZsaRDn/gGsbcj+M6VCm
\r
36 X-Received: by 10.112.9.104 with SMTP id y8mr3332656lba.132.1360404422035;
\r
37 Sat, 09 Feb 2013 02:07:02 -0800 (PST)
\r
38 Received: from localhost (dsl-hkibrasgw4-50df51-27.dhcp.inet.fi.
\r
40 by mx.google.com with ESMTPS id fh4sm10945726lbb.7.2013.02.09.02.06.59
\r
41 (version=TLSv1.2 cipher=RC4-SHA bits=128/128);
\r
42 Sat, 09 Feb 2013 02:07:01 -0800 (PST)
\r
43 From: Jani Nikula <jani@nikula.org>
\r
44 To: Albin Stjerna <albin.stjerna@gmail.com>, notmuch@notmuchmail.org
\r
45 Subject: Re: Bug: problem decoding some non-ascii characters in subjects
\r
46 In-Reply-To: <87pq09eu41.fsf@hecate.student.uu.se>
\r
47 References: <87txpnds0k.fsf@hecate.student.uu.se> <8738x7kq44.fsf@nikula.org>
\r
48 <87pq09eu41.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: Sat, 09 Feb 2013 12:06:58 +0200
\r
52 Message-ID: <87mwvd6bst.fsf@nikula.org>
\r
54 Content-Type: text/plain; charset=utf-8
\r
55 Content-Transfer-Encoding: quoted-printable
\r
57 ALoCoQnf7H6oeQAxJGM8/Qr//6aRqq8gmHuxZcIBYCPEBp5D5TjT5khZrGH1pH95OLh73c+8BkcE
\r
58 X-BeenThere: notmuch@notmuchmail.org
\r
59 X-Mailman-Version: 2.1.13
\r
61 List-Id: "Use and development of the notmuch mail system."
\r
62 <notmuch.notmuchmail.org>
\r
63 List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,
\r
64 <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>
\r
65 List-Archive: <http://notmuchmail.org/pipermail/notmuch>
\r
66 List-Post: <mailto:notmuch@notmuchmail.org>
\r
67 List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>
\r
68 List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,
\r
69 <mailto:notmuch-request@notmuchmail.org?subject=subscribe>
\r
70 X-List-Received-Date: Sat, 09 Feb 2013 10:07:07 -0000
\r
72 On Sat, 09 Feb 2013, Albin Stjerna <albin.stjerna@gmail.com> wrote:
\r
73 > Jani Nikula wrote:
\r
75 >> On Fri, 08 Feb 2013, Albin Stjerna <albin.stjerna@gmail.com> wrote:
\r
76 >> > I've been noticing that notmuch has some problems decoding certain
\r
77 >> > strangely-encoded non-ascii characters in certain emails. For example,
\r
78 >> > today I got this: [BIBLIST] Digitaliseringensprojektens skadliga
\r
79 >> > f=3D?ISO-8859-1?Q?=3DF6rk=3DE4rlek_f=3DF6r_?=3D PDF-formatet (should be
\r
80 >> > rendered: =C2=BBDigitaliseringsprojektens skadliga f=C3=B6rk=C3=A4rlek=
\r
82 >> > PDF-formatet=C2=AB).
\r
84 >> > Apparently, some metadata is passed on to help the MUA decode the
\r
85 >> > string, but notmuch doesn't seem to handle it. Entire emails can of
\r
86 >> > course be supplied as needed.
\r
88 >> Please copy paste the Subject: header directly from the message file.
\r
90 > The exact Subject: header (from the file, not notmuch) is:
\r
91 > Subject: [BIBLIST] Digitaliseringensprojektens skadliga f=3D?ISO-8859-1?Q=
\r
92 ?=3DF6rk=3DE4rlek_f=3DF6r_?=3D PDF-formatet
\r
94 Is that entirely on one line in the original message file? If not, where
\r
95 exactly is it split?
\r
97 Either way, at a glance, it seems like the encoding is malformed. I
\r
98 think the encoded-word ("=3D?" charset "?" encoding "?" encoded-text "?=3D")
\r
99 should be separated by space to make it an atom. [RFC 2047, RFC 2822].
\r
101 If you manually move the leading 'f' after the "?Q?" bit, it works as
\r
102 expected. It looks like the bug is in the sender's user agent.
\r