From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from localhost (localhost [127.0.0.1]) by olra.theworths.org (Postfix) with ESMTP id A2963431FD4 for ; Tue, 27 Aug 2013 04:21:23 -0700 (PDT) X-Virus-Scanned: Debian amavisd-new at olra.theworths.org X-Spam-Flag: NO X-Spam-Score: 0 X-Spam-Level: X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[none] autolearn=disabled Received: from olra.theworths.org ([127.0.0.1]) by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9NnucdZvML8l for ; Tue, 27 Aug 2013 04:21:18 -0700 (PDT) Received: from yantan.tethera.net (yantan.tethera.net [199.188.72.155]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by olra.theworths.org (Postfix) with ESMTPS id A3570431FAF for ; Tue, 27 Aug 2013 04:21:18 -0700 (PDT) Received: from remotemail by yantan.tethera.net with local (Exim 4.80) (envelope-from ) id 1VEHKn-0004rn-SD; Tue, 27 Aug 2013 08:21:17 -0300 Received: (nullmailer pid 11756 invoked by uid 1000); Tue, 27 Aug 2013 11:21:14 -0000 From: David Bremner To: Eric Abrahamsen , notmuch@notmuchmail.org Subject: Re: encoding when forwarding messages In-Reply-To: <87bo4jjv15.fsf@ericabrahamsen.net> References: <87bo4jjv15.fsf@ericabrahamsen.net> User-Agent: Notmuch/0.16 (http://notmuchmail.org) Emacs/24.3.1 (x86_64-pc-linux-gnu) Date: Tue, 27 Aug 2013 08:21:14 -0300 Message-ID: <87y57n8jmd.fsf@zancas.localnet> MIME-Version: 1.0 Content-Type: text/plain X-BeenThere: notmuch@notmuchmail.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: "Use and development of the notmuch mail system." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Aug 2013 11:21:23 -0000 Eric Abrahamsen writes: > I saw another message about the same problem on this list, in January, > with the advice to upgrade to git, but I'm still seeing it on notmuch > 0.16+7~gdc51bf0. Forwarding a message from within emacs using > `notmuch-mua-forward-message' sometimes produces garbled encoding. > Calling `notmuch-show-forward-message' on the same message, however, > creates what appears to be a raw message, properly encoded. > > Is there something still amiss in the code? Am I using the wrong > command? Do you really mean notmuch-mua-forward-message? That function is not interactive, which would make it more work to call. In any case, notmuch-show-forward-message does take some care to read the message in raw mode (via with-current-notmuch-show-message); when you call notmuch-mua*forward-message, how are you filling the buffer? d