--- /dev/null
+Return-Path: <albin.stjerna@gmail.com>\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 84134431FAF\r
+ for <notmuch@notmuchmail.org>; Sat, 5 Jan 2013 00:54:13 -0800 (PST)\r
+X-Virus-Scanned: Debian amavisd-new at olra.theworths.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: -0.799\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=-0.799 tagged_above=-999 required=5\r
+ tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1,\r
+ FREEMAIL_FROM=0.001, 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 EtqFsJr5w2UC for <notmuch@notmuchmail.org>;\r
+ Sat, 5 Jan 2013 00:54:13 -0800 (PST)\r
+Received: from mail-la0-f41.google.com (mail-la0-f41.google.com\r
+ [209.85.215.41]) (using TLSv1 with cipher RC4-SHA (128/128 bits))\r
+ (No client certificate requested)\r
+ by olra.theworths.org (Postfix) with ESMTPS id CD544431FAE\r
+ for <notmuch@notmuchmail.org>; Sat, 5 Jan 2013 00:54:12 -0800 (PST)\r
+Received: by mail-la0-f41.google.com with SMTP id em20so11118737lab.0\r
+ for <notmuch@notmuchmail.org>; Sat, 05 Jan 2013 00:54:11 -0800 (PST)\r
+DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;\r
+ h=x-received:from:to:cc:subject:user-agent:date:message-id\r
+ :mime-version:content-type:content-transfer-encoding;\r
+ bh=QZ9DCSJT94Y3hSPAA3M1R++Dg6UyAa6/gFRnx0iVS/w=;\r
+ b=Xa49MMtqGE+joP3bZAX8pvVQJXm/+pOlPhL08BtA9popVRRxVdaiOk7CiRTXeuHw96\r
+ oDIygbnwDws0nlSajW8yokM4nW/2kqc9wXywchuhURHmMREhpjOMshCqB56H9YF34cmD\r
+ e9l9MUytcqhPA6E97njLk/4nDwFB1WkML5Kklhd3fn7oih/BYhlAKlKycZy81N3wBx27\r
+ 0O/s7wjNFYsfe4vYGkieRGEp1MORzyYBqJqLDw5K1A9uXCYiiqPkoeG2T5RXS/h31WoJ\r
+ uqqK26Gqew6K5D8Y6iqrD7W6vBvhjW9eeSiZuJiwDiieO/w4/TZY7zoAuyKn+QQsQf6K\r
+ 5SNw==\r
+X-Received: by 10.112.28.9 with SMTP id x9mr22263814lbg.27.1357376049921;\r
+ Sat, 05 Jan 2013 00:54:09 -0800 (PST)\r
+Received: from hecate (nl110-96-173.student.uu.se. [130.242.96.173])\r
+ by mx.google.com with ESMTPS id fh4sm18641036lbb.7.2013.01.05.00.54.07\r
+ (version=TLSv1/SSLv3 cipher=OTHER);\r
+ Sat, 05 Jan 2013 00:54:08 -0800 (PST)\r
+From: Albin Stjerna <albin.stjerna@gmail.com>\r
+To: Notmuch Mail Mailing List <notmuch@notmuchmail.org>\r
+Cc: \r
+Subject: Unicode characters are incorrectly reproduced when forwarding mail\r
+User-Agent: Notmuch/0.14 (http://notmuchmail.org) Emacs/24.3.50.1\r
+ (x86_64-pc-linux-gnu)\r
+Date: Sat, 05 Jan 2013 09:54:03 +0100\r
+Message-ID: <8738yg3t90.fsf@hecate.student.uu.se>\r
+MIME-Version: 1.0\r
+Content-Type: text/plain; charset=utf-8\r
+Content-Transfer-Encoding: quoted-printable\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: Sat, 05 Jan 2013 08:54:13 -0000\r
+\r
+Hi!\r
+\r
+When forwarding an email containing (what I think is) unicode characters (p=\r
+rimarily umlauts), these are incorrectly re-entered as strange escaped char=\r
+acters (=C3=A4 becomes \344, =C3=A5 becomes \345 and so on). Then, when I t=\r
+ry to send the email, I get an error about the message containing unprintab=\r
+le characters.\r
+\r
+Interestingly enough, this problem does not occur in the headers (Subject, =\r
+>From etc), and the problem does not occur at all when quoting messages via =\r
+notmuch-reply. Also, it doesn't happen for all email messages, so it might =\r
+be an issue with the encoding. I think a common denominator for the un-forw=\r
+ardable messages is that they contain no charset=3D declaration, though the=\r
+y still render just fine.\r
+\r
+Any help debugging would be greatly appreciated!\r