From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Kenichi Handa Newsgroups: gmane.emacs.devel Subject: Re: rmail-forward Date: Fri, 14 Jan 2011 14:39:19 +0900 Message-ID: References: NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="=-=-=" X-Trace: dough.gmane.org 1294983585 26914 80.91.229.12 (14 Jan 2011 05:39:45 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Fri, 14 Jan 2011 05:39:45 +0000 (UTC) Cc: emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Jan 14 06:39:39 2011 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1PdcNu-00066Q-2u for ged-emacs-devel@m.gmane.org; Fri, 14 Jan 2011 06:39:38 +0100 Original-Received: from localhost ([127.0.0.1]:46363 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1PdcNt-0007kG-HV for ged-emacs-devel@m.gmane.org; Fri, 14 Jan 2011 00:39:37 -0500 Original-Received: from [140.186.70.92] (port=55771 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1PdcNk-0007kA-E2 for emacs-devel@gnu.org; Fri, 14 Jan 2011 00:39:29 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1PdcNj-0008WF-CK for emacs-devel@gnu.org; Fri, 14 Jan 2011 00:39:28 -0500 Original-Received: from mx1.aist.go.jp ([150.29.246.133]:63026) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1PdcNh-0008Sq-9Q; Fri, 14 Jan 2011 00:39:25 -0500 Original-Received: from rqsmtp2.aist.go.jp (rqsmtp2.aist.go.jp [150.29.254.123]) by mx1.aist.go.jp with ESMTP id p0E5dKJk006844; Fri, 14 Jan 2011 14:39:21 +0900 (JST) env-from (handa@m17n.org) Original-Received: from smtp4.aist.go.jp by rqsmtp2.aist.go.jp with ESMTP id p0E5dKcL023268; Fri, 14 Jan 2011 14:39:20 +0900 (JST) env-from (handa@m17n.org) Original-Received: by smtp4.aist.go.jp with ESMTP id p0E5dJMw006978; Fri, 14 Jan 2011 14:39:19 +0900 (JST) env-from (handa@m17n.org) Original-Received: from handa by etlken with local (Exim 4.71) (envelope-from ) id 1PdcNb-0004YX-OZ; Fri, 14 Jan 2011 14:39:19 +0900 In-Reply-To: (message from Eli Zaretskii on Thu, 13 Jan 2011 23:04:39 -0500) X-detected-operating-system: by eggs.gnu.org: Solaris 9 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:134522 Archived-At: --=-=-= Content-Type: text/plain In article , Eli Zaretskii writes: > rmail-forward lately began to format the forwarded messages weirdly. > It doesn't use the specially formatted lines delimiting the message, > that it used to use before, and instead inserts some weird looking > delimiters such as this one: > --=-=-= Content-Type: message/rfc822 Content-Disposition: inline Content-Transfer-Encoding: 8bit > It also inserts the forwarded message with all its headers, including > the ones created by Rmail for its own purposes, like > "X-RMAIL-ATTRIBUTES:". Previously, I could control whether these > headers are copied to the forwarded message by toggling their display > (with `t') in the RMAIL buffer prior to using `f' to forward the > message, and the default was not to copy these headers, only those > normally shown by rmail-show-message. > Is this a bug or a feature? If the latter, what is its purpose? It's a feature. When rmail-enable-mime is non-nil, message forwarding is also done in MIME style; i.e., the forwarding message is embeded in message/rfc822 entity of a multipart body. That whole work is done by message-forward-make-body-mime of message.el which I didn't touch. It seems that it'a policy of message.el to include all headers in a forwarding message except those matching with message-forward-ignored-headers (which currently doesn't include X-RMAIL-* but should include). MIME-capable MUA (includihng rmail-mime) anyway prunes the forwarded header accoding to it's policy (e.g. rmail-ignored-headers). Please test to forward some mail to yourself and see how it's shown to you by rmail. Re-forwarding that forwarded message generates a further nested MIME message. By the way, I first tried to use message-forward-rmail-make-body instead of message-forward-make-body-mime, but it signals an error while trying to un-prune the messsage header. It seems that message-forward-rmail-make-body is not yet adjusted for the new mbox-based rmail code. --- Kenichi Handa handa@m17n.org --=-=-=--