Re: encoding when forwarding messages

diff --git a/4e/459c811cf1e3a782aebfadcec73c3d1cdd7ce6 b/4e/459c811cf1e3a782aebfadcec73c3d1cdd7ce6
new file mode 100644 (file)
index 0000000..abdd2e3
--- /dev/null
+++ b/4e/459c811cf1e3a782aebfadcec73c3d1cdd7ce6
@@ -0,0 +1,99 @@
+Return-Path: <gmn-notmuch@m.gmane.org>\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 D0E86431FD4\r
+       for <notmuch@notmuchmail.org>; Tue, 27 Aug 2013 07:41:19 -0700 (PDT)\r
+X-Virus-Scanned: Debian amavisd-new at olra.theworths.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: 0.865\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=0.865 tagged_above=-999 required=5\r
+       tests=[RCVD_IN_DNSWL_NONE=-0.0001, RCVD_NUMERIC_HELO=0.865]\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 lDPiIEwjzjVG for <notmuch@notmuchmail.org>;\r
+       Tue, 27 Aug 2013 07:41:12 -0700 (PDT)\r
+Received: from plane.gmane.org (plane.gmane.org [80.91.229.3])\r
+       (using TLSv1 with cipher AES256-SHA (256/256 bits))\r
+       (No client certificate requested)\r
+       by olra.theworths.org (Postfix) with ESMTPS id 56F27431FAF\r
+       for <notmuch@notmuchmail.org>; Tue, 27 Aug 2013 07:41:12 -0700 (PDT)\r
+Received: from list by plane.gmane.org with local (Exim 4.69)\r
+       (envelope-from <gmn-notmuch@m.gmane.org>) id 1VEKSC-0007tJ-E3\r
+       for notmuch@notmuchmail.org; Tue, 27 Aug 2013 16:41:08 +0200\r
+Received: from 114.252.248.167 ([114.252.248.167])\r
+       by main.gmane.org with esmtp (Gmexim 0.1 (Debian))\r
+       id 1AlnuQ-0007hv-00\r
+       for <notmuch@notmuchmail.org>; Tue, 27 Aug 2013 16:41:08 +0200\r
+Received: from eric by 114.252.248.167 with local (Gmexim 0.1 (Debian))\r
+       id 1AlnuQ-0007hv-00\r
+       for <notmuch@notmuchmail.org>; Tue, 27 Aug 2013 16:41:08 +0200\r
+X-Injected-Via-Gmane: http://gmane.org/\r
+To: notmuch@notmuchmail.org\r
+From: Eric Abrahamsen <eric@ericabrahamsen.net>\r
+Subject: Re: encoding when forwarding messages\r
+Date: Tue, 27 Aug 2013 22:41:45 +0800\r
+Lines: 37\r
+Message-ID: <87fvtvi4ba.fsf@ericabrahamsen.net>\r
+References: <87bo4jjv15.fsf@ericabrahamsen.net>\r
+       <87y57n8jmd.fsf@zancas.localnet>\r
+Mime-Version: 1.0\r
+Content-Type: text/plain\r
+X-Complaints-To: usenet@ger.gmane.org\r
+X-Gmane-NNTP-Posting-Host: 114.252.248.167\r
+User-Agent: Gnus/5.130008 (Ma Gnus v0.8) Emacs/24.3 (gnu/linux)\r
+Cancel-Lock: sha1:xtidThf1aMewpXWBSG6ilW6PstY=\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: Tue, 27 Aug 2013 14:41:20 -0000\r
+\r
+David Bremner <david@tethera.net> writes:\r
+\r
+> Eric Abrahamsen <eric@ericabrahamsen.net> writes:\r
+>\r
+>> I saw another message about the same problem on this list, in January,\r
+>> with the advice to upgrade to git, but I'm still seeing it on notmuch\r
+>> 0.16+7~gdc51bf0. Forwarding a message from within emacs using\r
+>> `notmuch-mua-forward-message' sometimes produces garbled encoding.\r
+>> Calling `notmuch-show-forward-message' on the same message, however,\r
+>> creates what appears to be a raw message, properly encoded.\r
+>>\r
+>> Is there something still amiss in the code? Am I using the wrong\r
+>> command?\r
+>\r
+> Do you really mean notmuch-mua-forward-message? That function is not\r
+> interactive, which would make it more work to call.\r
+>\r
+> In any case, notmuch-show-forward-message does take some care to read\r
+> the message in raw mode (via with-current-notmuch-show-message); when\r
+> you call notmuch-mua*forward-message, how are you filling the buffer?\r
+>\r
+> d\r
+\r
+Sorry! It was `notmuch-mua-new-forward-message' I've been using,\r
+apologies for the confusion. I'm not calling any particular filling\r
+commands. I've got this in .gnus.el:\r
+\r
+(add-hook 'message-mode-hook\r
+         (lambda ()\r
+           (flyspell-mode)\r
+           (orgstruct-mode)))\r
+\r
+And I've got the auto-fill minor mode enabled. I don't see any other\r
+minor modes that seem likely to interfere...\r
+\r
+Thanks!\r
+Eric\r
+\r