1 Return-Path: <matt@bubblegen.co.uk>
\r
2 X-Original-To: notmuch@notmuchmail.org
\r
3 Delivered-To: notmuch@notmuchmail.org
\r
4 Received: from localhost (localhost [127.0.0.1])
\r
5 by arlo.cworth.org (Postfix) with ESMTP id 7BC416DE1502
\r
6 for <notmuch@notmuchmail.org>; Fri, 6 Nov 2015 11:31:11 -0800 (PST)
\r
7 X-Virus-Scanned: Debian amavisd-new at cworth.org
\r
11 X-Spam-Status: No, score=-0.26 tagged_above=-999 required=5 tests=[AWL=0.460,
\r
12 RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01,
\r
13 RCVD_IN_MSPIKE_WL=-0.01] autolearn=disabled
\r
14 Received: from arlo.cworth.org ([127.0.0.1])
\r
15 by localhost (arlo.cworth.org [127.0.0.1]) (amavisd-new, port 10024)
\r
16 with ESMTP id RkX7mPxkfY9Y for <notmuch@notmuchmail.org>;
\r
17 Fri, 6 Nov 2015 11:31:09 -0800 (PST)
\r
18 X-Greylist: delayed 457 seconds by postgrey-1.35 at arlo;
\r
19 Fri, 06 Nov 2015 11:31:08 PST
\r
20 Received: from avasout05.plus.net (avasout05.plus.net [84.93.230.250])
\r
21 by arlo.cworth.org (Postfix) with ESMTPS id D00396DE12E8
\r
22 for <notmuch@notmuchmail.org>; Fri, 6 Nov 2015 11:31:08 -0800 (PST)
\r
23 Received: from [192.168.1.11] ([80.229.236.194]) by avasout05 with smtp
\r
24 id eKPM1r0054CLJ5401KPQEz; Fri, 06 Nov 2015 19:23:26 +0000
\r
26 X-CNFS-Analysis: v=2.1 cv=MryvkDue c=1 sm=1 tr=0
\r
27 a=G4bc5lkgapKKm1P+Twxy3Q==:117 a=G4bc5lkgapKKm1P+Twxy3Q==:17 a=0Bzu9jTXAAAA:8
\r
28 a=80hmnl3cAAAA:8 a=kj9zAlcOel0A:10 a=skbIlk6SAAAA:8 a=y1xZCqX1Ovw6XMoibX0A:9
\r
30 References: <430FC760-8BF5-4798-89B5-E7F2A16564B7@bubblegen.co.uk>
\r
31 <87h9l0qg1p.fsf@alice.fifthhorseman.net>
\r
32 Mime-Version: 1.0 (1.0)
\r
33 In-Reply-To: <87h9l0qg1p.fsf@alice.fifthhorseman.net>
\r
34 Content-Type: text/plain;
\r
36 Content-Transfer-Encoding: quoted-printable
\r
37 Message-Id: <847CC903-FE82-49B4-A3D6-1070D58BF2F3@bubblegen.co.uk>
\r
38 Cc: "notmuch@notmuchmail.org" <notmuch@notmuchmail.org>
\r
39 X-Mailer: iPad Mail (12H143)
\r
40 From: Matthew Lear <matt@bubblegen.co.uk>
\r
41 Subject: Re: notmuch-emacs: forward messages inline
\r
42 Date: Fri, 6 Nov 2015 19:23:22 +0000
\r
43 To: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
\r
44 X-BeenThere: notmuch@notmuchmail.org
\r
45 X-Mailman-Version: 2.1.20
\r
47 List-Id: "Use and development of the notmuch mail system."
\r
48 <notmuch.notmuchmail.org>
\r
49 List-Unsubscribe: <https://notmuchmail.org/mailman/options/notmuch>,
\r
50 <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>
\r
51 List-Archive: <http://notmuchmail.org/pipermail/notmuch/>
\r
52 List-Post: <mailto:notmuch@notmuchmail.org>
\r
53 List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>
\r
54 List-Subscribe: <https://notmuchmail.org/mailman/listinfo/notmuch>,
\r
55 <mailto:notmuch-request@notmuchmail.org?subject=subscribe>
\r
56 X-List-Received-Date: Fri, 06 Nov 2015 19:31:11 -0000
\r
60 > On 5 Nov 2015, at 21:42, Daniel Kahn Gillmor <dkg@fifthhorseman.net> wrote=
\r
62 >> On Fri 2015-11-06 04:51:53 +0900, Matthew Lear wrote:
\r
63 >> Are there any recommended ways to selectively forward an email as
\r
64 >> inline with notmuch-emacs rather than as an RFC822 attachment, eg have
\r
65 >> a new shortcut key that can be used for this purpose in addition to f?
\r
66 >> I have toggled one of the mml configuration variables (I forget
\r
67 >> exactly what it was) which switched the forwarding method to inline
\r
68 >> (ACAICT this also removed the ability of being able to forward as
\r
69 >> RFC822), but it also included various header information in the body
\r
70 >> of the email. Not good.
\r
72 > I suppose you could reply to the message (r) and just change the
\r
73 > addresses, which would include the previous message "inline". If you
\r
74 > don't like that it leaks the previous message-id in the In-Reply-To and
\r
75 > References headers, you can just kill them from the buffer manually.
\r
77 I guess that's one way, but it's a bit of a faff. Unless it was possible to w=
\r
79 it all up in lisp, I don't really think it's a good option.
\r
81 > But can i ask why you'd want this? forwarded messages as RFC 822
\r
82 > attachments are significantly more sane for any MUA to deal with.
\r
84 No arguments on the 'being sane' front, although I have seen
\r
85 notmuch-emacs fail to correctly formulate an RFC822 attachment of the
\r
86 original email message a few times. I suspect this was due to MS Outlook
\r
87 formatting but can't be sure, though. My main use of notmuch is at work
\r
88 where I have to handle large amounts of email such as bug notifications from=
\r
90 a couple of systems, messages to/from lists, auto generated stuff for tracki=
\r
92 plus the usual reams of corporate email from teams and colleagues. Notmuch
\r
93 allows me to handle this fantastically. A common use case of forwarding
\r
94 messages inline is to take an email already received, and send it onto
\r
95 colleagues. It's not uncommon for this to initiate a new thread of conversat=
\r
97 and other people could be added to the thread as appropriate. If I were to
\r
98 forward a message I received as an RFC822 attachment, in order for the
\r
99 conversation to be coherent and contained in the text when other people were=
\r
101 added to the thread, the email containing my attachment would need to be
\r
102 forwarded to (additional) recipients because 'replying to all' and including=
\r
104 recipients wouldn't contain the original message. As I see it, to be able to=
\r
106 forward and include people starting a new thread based on the forwarded
\r
107 message, it needs to be inline. Make sense?
\r