--- /dev/null
+Return-Path: <tomi.ollila@iki.fi>\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 A9572431FB6\r
+ for <notmuch@notmuchmail.org>; Mon, 4 Jun 2012 03:09:21 -0700 (PDT)\r
+X-Virus-Scanned: Debian amavisd-new at olra.theworths.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: 0\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[none]\r
+ 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 niOi609wefny for <notmuch@notmuchmail.org>;\r
+ Mon, 4 Jun 2012 03:09:20 -0700 (PDT)\r
+Received: from guru.guru-group.fi (guru.guru-group.fi [46.183.73.34])\r
+ by olra.theworths.org (Postfix) with ESMTP id C89D5431FAF\r
+ for <notmuch@notmuchmail.org>; Mon, 4 Jun 2012 03:09:19 -0700 (PDT)\r
+Received: by guru.guru-group.fi (Postfix, from userid 501)\r
+ id 3F88510014D; Mon, 4 Jun 2012 13:09:29 +0300 (EEST)\r
+From: Tomi Ollila <tomi.ollila@iki.fi>\r
+To: Albin Stjerna <albin.stjerna@gmail.com>, notmuch@notmuchmail.org\r
+Subject: Re: Problem with invalid characters when using notmuch-reply\r
+In-Reply-To: <87r4tvmoeq.fsf@hecate.student.uu.se>\r
+References: <87r4tvmoeq.fsf@hecate.student.uu.se>\r
+User-Agent: Notmuch/0.13.2+7~g08be9ce (http://notmuchmail.org) Emacs/23.1.1\r
+ (x86_64-redhat-linux-gnu)\r
+X-Face: HhBM'cA~<r"^Xv\KRN0P{vn'Y"Kd;zg_y3S[4)KSN~s?O\"QPoL\r
+ $[Xv_BD:i/F$WiEWax}R(MPS`^UaptOGD`*/=@\1lKoVa9tnrg0TW?"r7aRtgk[F\r
+ !)g;OY^,BjTbr)Np:%c_o'jj,Z\r
+Date: Mon, 04 Jun 2012 13:09:28 +0300\r
+Message-ID: <m2haurl76v.fsf@guru.guru-group.fi>\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: Mon, 04 Jun 2012 10:09:21 -0000\r
+\r
+On Mon, Jun 04 2012, Albin Stjerna <albin.stjerna@gmail.com> wrote:\r
+\r
+> Hi!\r
+>\r
+> I have a very confusing problem. When replying to a message containing\r
+> special characters (read: non-ascii), they show up as mysteriously\r
+> escaped characters, such as \345 (where the letter =C3=A4 should be). When\r
+> sending these replies, I get an error about my message containing\r
+> non-printable characters. When these messages arrive, the special\r
+> characters (even those I entered, that looked fine in the mail compose\r
+> buffer) are garbled.\r
+>\r
+> Everything works fine when composing a new message. The problem only\r
+> appears when replying. The problem appeared quite recently, apparently\r
+> out of nowhere. No emacs upgrade, no notmuch upgrade (as far as I can\r
+> recall).\r
+>\r
+> The problem is appears in both Emacs 23 and 24, and restart (neither of E=\r
+macs nor of my computer) doesn't help.\r
+>\r
+> Also:\r
+> albin@hecate ~ % notmuch --version\r
+> notmuch 0.13\r
+\r
+Notmuch 0.13.1 fixed this problem -- excerpt from NEWS file:\r
+\r
+Notmuch 0.13.1 (2012-05-29)\r
+=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=\r
+=3D=3D\r
+\r
+Bug-fix release\r
+---------------\r
+\r
+Fix inserting of UTF-8 characters from *text/plain* parts in reply\r
+\r
+ While notmuch gained ability to insert content from other than\r
+ *text/plain*\r
+ parts of email whenever *text/plain* parts are not available (notably\r
+ HTML-only emails), replying to mails that do have *text/plain* the\r
+ non-ASCII characters were incorrectly decoded. This is now fixed.\r
+\r
+\r
+>\r
+> albin@hecate ~ % locale\r
+> LANG=3Den_US.utf8\r
+> LANGUAGE=3D\r
+> LC_CTYPE=3D"en_US.utf8"\r
+> LC_NUMERIC=3D"en_US.utf8"\r
+> LC_TIME=3D"en_US.utf8"\r
+> LC_COLLATE=3D"en_US.utf8"\r
+> LC_MONETARY=3D"en_US.utf8"\r
+> LC_MESSAGES=3D"en_US.utf8"\r
+> LC_PAPER=3D"en_US.utf8"\r
+> LC_NAME=3D"en_US.utf8"\r
+> LC_ADDRESS=3D"en_US.utf8"\r
+> LC_TELEPHONE=3D"en_US.utf8"\r
+> LC_MEASUREMENT=3D"en_US.utf8"\r
+> LC_IDENTIFICATION=3D"en_US.utf8"\r
+> LC_ALL=3D\r
+>\r
+> notmuch reply (on the command line) seems to work just fine.\r
+>\r
+> Any pointers you can give me would be greatly appreciated!\r
+\r
+Thank you for the good information you provided in your report!\r
+\r
+> Thanks in advance,\r
+> Albin\r
+\r
+Tomi\r