--- /dev/null
+Return-Path: <matt@bubblegen.co.uk>\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 7BC416DE1502\r
+ for <notmuch@notmuchmail.org>; Fri, 6 Nov 2015 11:31:11 -0800 (PST)\r
+X-Virus-Scanned: Debian amavisd-new at cworth.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: -0.26\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=-0.26 tagged_above=-999 required=5 tests=[AWL=0.460, \r
+ RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01,\r
+ RCVD_IN_MSPIKE_WL=-0.01] 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 RkX7mPxkfY9Y for <notmuch@notmuchmail.org>;\r
+ Fri, 6 Nov 2015 11:31:09 -0800 (PST)\r
+X-Greylist: delayed 457 seconds by postgrey-1.35 at arlo;\r
+ Fri, 06 Nov 2015 11:31:08 PST\r
+Received: from avasout05.plus.net (avasout05.plus.net [84.93.230.250])\r
+ by arlo.cworth.org (Postfix) with ESMTPS id D00396DE12E8\r
+ for <notmuch@notmuchmail.org>; Fri, 6 Nov 2015 11:31:08 -0800 (PST)\r
+Received: from [192.168.1.11] ([80.229.236.194]) by avasout05 with smtp\r
+ id eKPM1r0054CLJ5401KPQEz; Fri, 06 Nov 2015 19:23:26 +0000\r
+X-CM-Score: 0.00\r
+X-CNFS-Analysis: v=2.1 cv=MryvkDue c=1 sm=1 tr=0\r
+ a=G4bc5lkgapKKm1P+Twxy3Q==:117 a=G4bc5lkgapKKm1P+Twxy3Q==:17 a=0Bzu9jTXAAAA:8\r
+ a=80hmnl3cAAAA:8 a=kj9zAlcOel0A:10 a=skbIlk6SAAAA:8 a=y1xZCqX1Ovw6XMoibX0A:9\r
+ a=CjuIK1q_8ugA:10\r
+References: <430FC760-8BF5-4798-89B5-E7F2A16564B7@bubblegen.co.uk>\r
+ <87h9l0qg1p.fsf@alice.fifthhorseman.net>\r
+Mime-Version: 1.0 (1.0)\r
+In-Reply-To: <87h9l0qg1p.fsf@alice.fifthhorseman.net>\r
+Content-Type: text/plain;\r
+ charset=us-ascii\r
+Content-Transfer-Encoding: quoted-printable\r
+Message-Id: <847CC903-FE82-49B4-A3D6-1070D58BF2F3@bubblegen.co.uk>\r
+Cc: "notmuch@notmuchmail.org" <notmuch@notmuchmail.org>\r
+X-Mailer: iPad Mail (12H143)\r
+From: Matthew Lear <matt@bubblegen.co.uk>\r
+Subject: Re: notmuch-emacs: forward messages inline\r
+Date: Fri, 6 Nov 2015 19:23:22 +0000\r
+To: Daniel Kahn Gillmor <dkg@fifthhorseman.net>\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: Fri, 06 Nov 2015 19:31:11 -0000\r
+\r
+Hi Daniel,\r
+\r
+> On 5 Nov 2015, at 21:42, Daniel Kahn Gillmor <dkg@fifthhorseman.net> wrote=\r
+:\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
+>=20\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 w=\r
+rap\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
+\r
+a couple of systems, messages to/from lists, auto generated stuff for tracki=\r
+ng,\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 conversat=\r
+ion\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
+\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=\r
+ new\r
+recipients wouldn't contain the original message. As I see it, to be able to=\r
+\r
+forward and include people starting a new thread based on the forwarded\r
+message, it needs to be inline. Make sense?\r
+-- Matt=20=\r
projects / notmuch-archives.git / commitdiff