--- /dev/null
+Return-Path: <markwalters1009@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 arlo.cworth.org (Postfix) with ESMTP id 2D5D76DE141B\r
+ for <notmuch@notmuchmail.org>; Mon, 9 Nov 2015 06:59:07 -0800 (PST)\r
+X-Virus-Scanned: Debian amavisd-new at cworth.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: 0.185\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=0.185 tagged_above=-999 required=5 tests=[AWL=0.055, \r
+ DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1,\r
+ FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001,\r
+ RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001]\r
+ autolearn=disabled\r
+Received: from arlo.cworth.org ([127.0.0.1])\r
+ by localhost (arlo.cworth.org [127.0.0.1]) (amavisd-new, port 10024)\r
+ with ESMTP id NQVxIi1r2jjk for <notmuch@notmuchmail.org>;\r
+ Mon, 9 Nov 2015 06:59:04 -0800 (PST)\r
+Received: from mail-wm0-f52.google.com (mail-wm0-f52.google.com\r
+ [74.125.82.52]) by arlo.cworth.org (Postfix) with ESMTPS id 3FBC96DE1348 for\r
+ <notmuch@notmuchmail.org>; Mon, 9 Nov 2015 06:59:04 -0800 (PST)\r
+Received: by wmnn186 with SMTP id n186so108433684wmn.1\r
+ for <notmuch@notmuchmail.org>; Mon, 09 Nov 2015 06:59:01 -0800 (PST)\r
+DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;\r
+ h=from:to:cc:subject:in-reply-to:references:user-agent:date\r
+ :message-id:mime-version:content-type;\r
+ bh=9w8NPj9gXoFhtAynau/nDoz6rAGXAYLOpClEgPlogcY=;\r
+ b=yaRIVEdQdLMIKLUPeEPjaeUAUqngzyO8UjJHRSlkx6vjKsFT9vCVkaqKM4xTHXRT79\r
+ uzINqLygDe90yP7KIadbLawh1lvf/8yt1Ad2dAyFCQwEs36ua35Y5607hFiFI1/MoRdR\r
+ LNz9pZdQpp+GyYkREZBlpiR9ApR09JZTwUyk/FsS3nYqit/J60IBqVi2ZGBIT/BjA7TH\r
+ X8ST3WFDUkc1nTJJ7Lx0qRD7qv6hwLwQYbGtqkRaCIV3Ye9mutsqQ0VemNVzaqmZsyag\r
+ QEX4pTyvzMgJ468k79rnQIxIm1CLV/vM6vkUEh1HX/cOPGlKgLv25i+SHbn5qiMCme4L\r
+ DRrw==\r
+X-Received: by 10.194.77.174 with SMTP id t14mr30693178wjw.23.1447081141229;\r
+ Mon, 09 Nov 2015 06:59:01 -0800 (PST)\r
+Received: from localhost (5751dfa2.skybroadband.com. [87.81.223.162])\r
+ by smtp.gmail.com with ESMTPSA id lb2sm15870117wjc.15.2015.11.09.06.58.59\r
+ (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);\r
+ Mon, 09 Nov 2015 06:59:00 -0800 (PST)\r
+From: Mark Walters <markwalters1009@gmail.com>\r
+To: Matthew Lear <matt@bubblegen.co.uk>,\r
+ Daniel Kahn Gillmor <dkg@fifthhorseman.net>\r
+Cc: "notmuch\@notmuchmail.org" <notmuch@notmuchmail.org>\r
+Subject: Re: notmuch-emacs: forward messages inline\r
+In-Reply-To: <847CC903-FE82-49B4-A3D6-1070D58BF2F3@bubblegen.co.uk>\r
+References: <430FC760-8BF5-4798-89B5-E7F2A16564B7@bubblegen.co.uk>\r
+ <87h9l0qg1p.fsf@alice.fifthhorseman.net>\r
+ <847CC903-FE82-49B4-A3D6-1070D58BF2F3@bubblegen.co.uk>\r
+User-Agent: Notmuch/0.18+519~ga09e253 (http://notmuchmail.org) Emacs/23.4.1\r
+ (x86_64-pc-linux-gnu)\r
+Date: Mon, 09 Nov 2015 14:58:58 +0000\r
+Message-ID: <871tbz8bil.fsf@qmul.ac.uk>\r
+MIME-Version: 1.0\r
+Content-Type: text/plain; charset=us-ascii\r
+X-BeenThere: notmuch@notmuchmail.org\r
+X-Mailman-Version: 2.1.20\r
+Precedence: list\r
+List-Id: "Use and development of the notmuch mail system."\r
+ <notmuch.notmuchmail.org>\r
+List-Unsubscribe: <https://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: <https://notmuchmail.org/mailman/listinfo/notmuch>,\r
+ <mailto:notmuch-request@notmuchmail.org?subject=subscribe>\r
+X-List-Received-Date: Mon, 09 Nov 2015 14:59:07 -0000\r
+\r
+\r
+Hi\r
+\r
+Does adding something like the following to your .emacs file do what you want?\r
+\r
+\r
+(defun my-forward (prefix)\r
+ (interactive "P")\r
+ (let ((message-forward-as-mime nil)\r
+ (message-forward-ignored-headers ".*"))\r
+ (notmuch-show-forward-message prefix)))\r
+\r
+(define-key notmuch-show-mode-map "F" 'my-forward)\r
+\r
+Then "F" should forward the message as a plain message rather than\r
+rfc822, and there should not be any spurious headers.\r
+\r
+Best wishes\r
+\r
+Mark\r
+\r
+\r
+\r
+On Fri, 06 Nov 2015, Matthew Lear <matt@bubblegen.co.uk> wrote:\r
+> Hi Daniel,\r
+>\r
+>> On 5 Nov 2015, at 21:42, Daniel Kahn Gillmor <dkg@fifthhorseman.net> wrote:\r
+>>> On Fri 2015-11-06 04:51:53 +0900, Matthew Lear wrote:\r
+>>> Are there any recommended ways to selectively forward an email as\r
+>>> inline with notmuch-emacs rather than as an RFC822 attachment, eg have\r
+>>> a new shortcut key that can be used for this purpose in addition to f?\r
+>>> I have toggled one of the mml configuration variables (I forget\r
+>>> exactly what it was) which switched the forwarding method to inline\r
+>>> (ACAICT this also removed the ability of being able to forward as\r
+>>> RFC822), but it also included various header information in the body\r
+>>> of the email. Not good.\r
+>> \r
+>> I suppose you could reply to the message (r) and just change the\r
+>> addresses, which would include the previous message "inline". If you\r
+>> don't like that it leaks the previous message-id in the In-Reply-To and\r
+>> References headers, you can just kill them from the buffer manually.\r
+>\r
+> I guess that's one way, but it's a bit of a faff. Unless it was possible to wrap\r
+> it all up in lisp, I don't really think it's a good option.\r
+>\r
+>> But can i ask why you'd want this? forwarded messages as RFC 822\r
+>> attachments are significantly more sane for any MUA to deal with.\r
+>\r
+> No arguments on the 'being sane' front, although I have seen\r
+> notmuch-emacs fail to correctly formulate an RFC822 attachment of the\r
+> original email message a few times. I suspect this was due to MS Outlook\r
+> formatting but can't be sure, though. My main use of notmuch is at work\r
+> where I have to handle large amounts of email such as bug notifications from\r
+> a couple of systems, messages to/from lists, auto generated stuff for tracking,\r
+> plus the usual reams of corporate email from teams and colleagues. Notmuch\r
+> allows me to handle this fantastically. A common use case of forwarding\r
+> messages inline is to take an email already received, and send it onto\r
+> colleagues. It's not uncommon for this to initiate a new thread of conversation\r
+> and other people could be added to the thread as appropriate. If I were to\r
+> forward a message I received as an RFC822 attachment, in order for the\r
+> conversation to be coherent and contained in the text when other people were\r
+> added to the thread, the email containing my attachment would need to be\r
+> forwarded to (additional) recipients because 'replying to all' and including new\r
+> recipients wouldn't contain the original message. As I see it, to be able to\r
+> forward and include people starting a new thread based on the forwarded\r
+> message, it needs to be inline. Make sense?\r
+> -- Matt \r
+> _______________________________________________\r
+> notmuch mailing list\r
+> notmuch@notmuchmail.org\r
+> https://notmuchmail.org/mailman/listinfo/notmuch\r
projects / notmuch-archives.git / commitdiff