unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Kenichi Handa <handa@m17n.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: rmail-forward
Date: Fri, 14 Jan 2011 14:39:19 +0900	[thread overview]
Message-ID: <tl739owyrg8.fsf@m17n.org> (raw)
In-Reply-To: <E1Pdatz-0001V4-T7@fencepost.gnu.org> (message from Eli Zaretskii on Thu, 13 Jan 2011 23:04:39 -0500)

[-- Attachment #1: Type: text/plain, Size: 335 bytes --]

In article <E1Pdatz-0001V4-T7@fencepost.gnu.org>, Eli Zaretskii <eliz@gnu.org> 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:

>   

[-- Attachment #2: Type: message/rfc822, Size: 1615 bytes --]


> 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

      reply	other threads:[~2011-01-14  5:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-14  4:04 rmail-forward Eli Zaretskii
2011-01-14  5:39 ` Kenichi Handa [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=tl739owyrg8.fsf@m17n.org \
    --to=handa@m17n.org \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).