From: Matthew Lear Date: Fri, 6 Nov 2015 19:23:22 +0000 (+0000) Subject: Re: notmuch-emacs: forward messages inline X-Git-Url: http://git.tremily.us/?a=commitdiff_plain;h=bd60f1da1d388a9c7842d32c26f33b73490f12f9;p=notmuch-archives.git Re: notmuch-emacs: forward messages inline --- diff --git a/05/01e99bd15d21b5f9fe4ffc270f19192993cf17 b/05/01e99bd15d21b5f9fe4ffc270f19192993cf17 new file mode 100644 index 000000000..2a5223c81 --- /dev/null +++ b/05/01e99bd15d21b5f9fe4ffc270f19192993cf17 @@ -0,0 +1,108 @@ +Return-Path: +X-Original-To: notmuch@notmuchmail.org +Delivered-To: notmuch@notmuchmail.org +Received: from localhost (localhost [127.0.0.1]) + by arlo.cworth.org (Postfix) with ESMTP id 7BC416DE1502 + for ; Fri, 6 Nov 2015 11:31:11 -0800 (PST) +X-Virus-Scanned: Debian amavisd-new at cworth.org +X-Spam-Flag: NO +X-Spam-Score: -0.26 +X-Spam-Level: +X-Spam-Status: No, score=-0.26 tagged_above=-999 required=5 tests=[AWL=0.460, + RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, + RCVD_IN_MSPIKE_WL=-0.01] autolearn=disabled +Received: from arlo.cworth.org ([127.0.0.1]) + by localhost (arlo.cworth.org [127.0.0.1]) (amavisd-new, port 10024) + with ESMTP id RkX7mPxkfY9Y for ; + Fri, 6 Nov 2015 11:31:09 -0800 (PST) +X-Greylist: delayed 457 seconds by postgrey-1.35 at arlo; + Fri, 06 Nov 2015 11:31:08 PST +Received: from avasout05.plus.net (avasout05.plus.net [84.93.230.250]) + by arlo.cworth.org (Postfix) with ESMTPS id D00396DE12E8 + for ; Fri, 6 Nov 2015 11:31:08 -0800 (PST) +Received: from [192.168.1.11] ([80.229.236.194]) by avasout05 with smtp + id eKPM1r0054CLJ5401KPQEz; Fri, 06 Nov 2015 19:23:26 +0000 +X-CM-Score: 0.00 +X-CNFS-Analysis: v=2.1 cv=MryvkDue c=1 sm=1 tr=0 + a=G4bc5lkgapKKm1P+Twxy3Q==:117 a=G4bc5lkgapKKm1P+Twxy3Q==:17 a=0Bzu9jTXAAAA:8 + a=80hmnl3cAAAA:8 a=kj9zAlcOel0A:10 a=skbIlk6SAAAA:8 a=y1xZCqX1Ovw6XMoibX0A:9 + a=CjuIK1q_8ugA:10 +References: <430FC760-8BF5-4798-89B5-E7F2A16564B7@bubblegen.co.uk> + <87h9l0qg1p.fsf@alice.fifthhorseman.net> +Mime-Version: 1.0 (1.0) +In-Reply-To: <87h9l0qg1p.fsf@alice.fifthhorseman.net> +Content-Type: text/plain; + charset=us-ascii +Content-Transfer-Encoding: quoted-printable +Message-Id: <847CC903-FE82-49B4-A3D6-1070D58BF2F3@bubblegen.co.uk> +Cc: "notmuch@notmuchmail.org" +X-Mailer: iPad Mail (12H143) +From: Matthew Lear +Subject: Re: notmuch-emacs: forward messages inline +Date: Fri, 6 Nov 2015 19:23:22 +0000 +To: Daniel Kahn Gillmor +X-BeenThere: notmuch@notmuchmail.org +X-Mailman-Version: 2.1.20 +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: Fri, 06 Nov 2015 19:31:11 -0000 + +Hi Daniel, + +> On 5 Nov 2015, at 21:42, Daniel Kahn Gillmor wrote= +: +>> On Fri 2015-11-06 04:51:53 +0900, Matthew Lear wrote: +>> Are there any recommended ways to selectively forward an email as +>> inline with notmuch-emacs rather than as an RFC822 attachment, eg have +>> a new shortcut key that can be used for this purpose in addition to f? +>> I have toggled one of the mml configuration variables (I forget +>> exactly what it was) which switched the forwarding method to inline +>> (ACAICT this also removed the ability of being able to forward as +>> RFC822), but it also included various header information in the body +>> of the email. Not good. +>=20 +> I suppose you could reply to the message (r) and just change the +> addresses, which would include the previous message "inline". If you +> don't like that it leaks the previous message-id in the In-Reply-To and +> References headers, you can just kill them from the buffer manually. + +I guess that's one way, but it's a bit of a faff. Unless it was possible to w= +rap +it all up in lisp, I don't really think it's a good option. + +> But can i ask why you'd want this? forwarded messages as RFC 822 +> attachments are significantly more sane for any MUA to deal with. + +No arguments on the 'being sane' front, although I have seen +notmuch-emacs fail to correctly formulate an RFC822 attachment of the +original email message a few times. I suspect this was due to MS Outlook +formatting but can't be sure, though. My main use of notmuch is at work +where I have to handle large amounts of email such as bug notifications from= + +a couple of systems, messages to/from lists, auto generated stuff for tracki= +ng, +plus the usual reams of corporate email from teams and colleagues. Notmuch +allows me to handle this fantastically. A common use case of forwarding +messages inline is to take an email already received, and send it onto +colleagues. It's not uncommon for this to initiate a new thread of conversat= +ion +and other people could be added to the thread as appropriate. If I were to +forward a message I received as an RFC822 attachment, in order for the +conversation to be coherent and contained in the text when other people were= + +added to the thread, the email containing my attachment would need to be +forwarded to (additional) recipients because 'replying to all' and including= + new +recipients wouldn't contain the original message. As I see it, to be able to= + +forward and include people starting a new thread based on the forwarded +message, it needs to be inline. Make sense? +-- Matt=20=