From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Richard Stallman Newsgroups: gmane.emacs.devel Subject: Re: Change in rmail-insert-mime-forwarded-message Date: Wed, 09 Jan 2013 11:43:15 -0500 Message-ID: References: <87ehhwtjgv.fsf@foil.strangled.net> Reply-To: rms@gnu.org NNTP-Posting-Host: plane.gmane.org Content-Type: text/plain; charset=ISO-8859-15 X-Trace: ger.gmane.org 1357749805 19649 80.91.229.3 (9 Jan 2013 16:43:25 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 9 Jan 2013 16:43:25 +0000 (UTC) Cc: emacs-devel@gnu.org To: mdl@alum.mit.edu Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Jan 09 17:43:43 2013 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1Tsykb-0007I1-RR for ged-emacs-devel@m.gmane.org; Wed, 09 Jan 2013 17:43:37 +0100 Original-Received: from localhost ([::1]:40833 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TsykM-00018p-6L for ged-emacs-devel@m.gmane.org; Wed, 09 Jan 2013 11:43:22 -0500 Original-Received: from eggs.gnu.org ([208.118.235.92]:47287) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TsykI-00016n-VG for emacs-devel@gnu.org; Wed, 09 Jan 2013 11:43:20 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1TsykG-0003TJ-S9 for emacs-devel@gnu.org; Wed, 09 Jan 2013 11:43:18 -0500 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:52539) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TsykG-0003TE-Oe for emacs-devel@gnu.org; Wed, 09 Jan 2013 11:43:16 -0500 Original-Received: from rms by fencepost.gnu.org with local (Exim 4.71) (envelope-from ) id 1TsykF-0007kw-Q6; Wed, 09 Jan 2013 11:43:15 -0500 In-reply-to: <87ehhwtjgv.fsf@foil.strangled.net> (message from Mark Lillibridge on Mon, 07 Jan 2013 19:57:36 -0800) X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2001:4830:134:3::e X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:156174 Archived-At: (1) forward the exact original message with all formatting and attachments included. That pretty much has to be done via an RFC822(sp?) attachment of the original message as received. As noted by bug #9766, some email clients are unable to display such attachments. (2) include the text seen by the Rmail user at the time forward is called. Both of these were possible before your change. The first was done with v f and the second with plain f. I do not think we should use RFC822(?) message attachments for this: I haven't read all the relevant RFC's, but I assume the destination email client will attempt to display an RFC822(sp?) message attachment as if it was a separately received message. f always puts the forwarded message into mime attachment, and there is no problem in this case. The message _as displayed in rmail_ does not contain mime part headers. It has things like this [1:text/plain Hide] instead. E.g., deal with its in-line multipart alternative parts appropriately, etc. If you attach an invalid message (e.g., bad MIME headers), I would expect the recipient to see garbage or an error message for the message attachment. The problem would never happen when sending the message as mime-processed by Rmail. (3) A smarter version of (2) that both makes the original message body visible to the destination client even for clients that don't handle RFC message attachments I can't make concrete sense of that, sorry. At the moment, in the absence of availability of (3), I use (1) for forward and use resend message to deal with people with limited mailers. I don't think (2) is a reasonable default because it drops attachments, formatting, and doesn't work for HTML-only messages. With your change, only (1) is possible. I think (2) is the right default, but in any case, it is better to have both options. So I think I will revert your change. -- Dr Richard Stallman President, Free Software Foundation 51 Franklin St Boston MA 02110 USA www.fsf.org www.gnu.org Skype: No way! That's nonfree (freedom-denying) software. Use Ekiga or an ordinary phone call