--- /dev/null
+Return-Path: <ethan.glasser.camp@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 D38A9431FBF\r
+ for <notmuch@notmuchmail.org>; Sun, 18 Nov 2012 10:03:01 -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 GjEcFIKrN8JQ for <notmuch@notmuchmail.org>;\r
+ Sun, 18 Nov 2012 10:03:01 -0800 (PST)\r
+Received: from mail-qa0-f46.google.com (mail-qa0-f46.google.com\r
+ [209.85.216.46]) (using TLSv1 with cipher RC4-SHA (128/128 bits))\r
+ (No client certificate requested)\r
+ by olra.theworths.org (Postfix) with ESMTPS id 0C502431FAF\r
+ for <notmuch@notmuchmail.org>; Sun, 18 Nov 2012 10:03:01 -0800 (PST)\r
+Received: by mail-qa0-f46.google.com with SMTP id c11so5124579qad.5\r
+ for <notmuch@notmuchmail.org>; Sun, 18 Nov 2012 10:02:59 -0800 (PST)\r
+DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;\r
+ h=from:to:subject:in-reply-to:references:user-agent:date:message-id\r
+ :mime-version:content-type;\r
+ bh=1XADBRoCphqtOiwxp6b7g2eC8G6KSxZyDq8JFv5tArE=;\r
+ b=z0tpuQiKvb8lxLYK9M+w0cE2o2PF9oZRnziVb0xeb/nGeOIC6HtdfByVZcBTrzq1vD\r
+ v/yA2b7iPtzc9kmZqBRSdWPCe/Wgz0n7Saulj5zcAYBG3km/rUM8C0zTutcLkTJ4OMso\r
+ wFAAITc8t2HBM+fCCq43y+3uy5dlgWIoqxQJXJEDkhxAwJQ6A9VklmOhA+YFcxDUqH6n\r
+ 8H8beJPE5abBo124ZypXAgipzH/biSmsnLqrnyXh7A5USJRZ7Slxr79hInEGvyQFac08\r
+ Rmk9hCn3HkkMvE9DL/+3rEsZNqzveZAivWAltGIETR0OllOFxNHV9sTjXiJQi25+LQhX\r
+ H4Iw==\r
+Received: by 10.224.78.148 with SMTP id l20mr9766424qak.27.1353261779189;\r
+ Sun, 18 Nov 2012 10:02:59 -0800 (PST)\r
+Received: from smtp.gmail.com ([66.114.71.21])\r
+ by mx.google.com with ESMTPS id em3sm4805880qab.12.2012.11.18.10.02.57\r
+ (version=TLSv1/SSLv3 cipher=OTHER);\r
+ Sun, 18 Nov 2012 10:02:58 -0800 (PST)\r
+From: Ethan Glasser-Camp <ethan.glasser.camp@gmail.com>\r
+To: Ethan Glasser-Camp <ethan.glasser.camp@gmail.com>,\r
+ Tomi Ollila <tomi.ollila@iki.fi>,\r
+ Michael Stapelberg <michael+nm@stapelberg.de>, notmuch@notmuchmail.org\r
+Subject: Re: [BUG] Saving attachments containing UTF-8 chars\r
+In-Reply-To: <87zk2f1nt0.fsf@betacantrips.com>\r
+References: <x6sj8xiexi.fsf@midna.zekjur.net>\r
+ <m2pq416xzl.fsf@guru.guru-group.fi>\r
+ <87zk2f1nt0.fsf@betacantrips.com>\r
+User-Agent: Notmuch/0.14+45~g6ea9330 (http://notmuchmail.org) Emacs/24.1.1\r
+ (x86_64-pc-linux-gnu)\r
+Date: Sun, 18 Nov 2012 13:02:55 -0500\r
+Message-ID: <87txsm23hs.fsf@betacantrips.com>\r
+MIME-Version: 1.0\r
+Content-Type: text/plain\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: Sun, 18 Nov 2012 18:03:02 -0000\r
+\r
+Ethan Glasser-Camp <ethan.glasser.camp@gmail.com> writes:\r
+\r
+> Writing this buffer using C-x C-w encodes it correctly too. So I think\r
+> this is an emacs MIME problem. We call mm-save-part, which calls\r
+> mm-save-part-to-file, which calls mm-with-unibyte-buffer. Hmm..\r
+>\r
+> Indeed, it seems that inserting this character into a file that's been\r
+> marked "unibyte" using (set-buffer-multibyte nil) turns it into the ^Y\r
+> character (ASCII code 0x19 -- the character that comes out in the patch\r
+> file). There's probably a technical reason that this should be true, but\r
+> I can't think of why that would be.\r
+\r
+The more I think about this, the more convinced I become that this is a\r
+bug in emacs's multibyte handling. I've filed a bug, see:\r
+\r
+http://debbugs.gnu.org/cgi/bugreport.cgi?bug=12925\r
+\r
+But I think Tomi's going to formalize his hacky patch and send that out\r
+later too. When he does, it has my +1.\r
+\r
+Ethan\r