From: Eli Zaretskii <eliz@gnu.org>
To: rms@gnu.org
Cc: mark.lillibridge@hp.com, emacs-devel@gnu.org
Subject: Re: Change in rmail-insert-mime-forwarded-message
Date: Wed, 09 Jan 2013 19:15:15 +0200 [thread overview]
Message-ID: <83obgygtwc.fsf@gnu.org> (raw)
In-Reply-To: <E1TsOey-0001Yr-6z@fencepost.gnu.org>
> Date: Mon, 07 Jan 2013 21:11:24 -0500
> From: Richard Stallman <rms@gnu.org>
> CC: mark.lillibridge@hp.com, emacs-devel@gnu.org
>
> The question is, is it right to send the undecoded message
> or is it better to send what is visible?
You can only send what is visible if the attachment was human-readable
text. You cannot do that with binary attachments.
Also, if the mail you forward has both text and HTML format, the
recipient will be unable to display HTML or text depending on her mail
agent, but will see both of them.
So I think it is better to send them encoded, so they appear as
attachments on the receiving side.
next prev parent reply other threads:[~2013-01-09 17:15 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-07 2:18 Change in rmail-insert-mime-forwarded-message Richard Stallman
2013-01-07 3:44 ` Eli Zaretskii
2013-01-08 2:11 ` Richard Stallman
2013-01-09 17:15 ` Eli Zaretskii [this message]
2013-01-10 6:19 ` Richard Stallman
2013-01-10 19:03 ` Eli Zaretskii
2013-01-07 4:43 ` Mark Lillibridge
2013-01-08 2:11 ` Richard Stallman
2013-01-08 3:57 ` Mark Lillibridge
2013-01-08 10:02 ` Stephen J. Turnbull
2013-01-08 16:32 ` Mark Lillibridge
2013-01-08 18:13 ` Stephen J. Turnbull
2013-01-23 0:32 ` Mark Lillibridge
2013-01-23 6:44 ` Stephen J. Turnbull
2013-01-09 16:43 ` Richard Stallman
2013-01-10 16:53 ` Mark Lillibridge
2013-01-11 4:43 ` Richard Stallman
2013-01-11 8:10 ` Eli Zaretskii
2013-01-11 16:48 ` Mark Lillibridge
2013-01-13 22:43 ` Richard Stallman
2013-01-14 22:43 ` Richard Stallman
2013-01-15 2:13 ` Glenn Morris
2013-01-15 4:01 ` Eli Zaretskii
2013-01-15 5:27 ` Richard Stallman
2013-01-15 16:07 ` Eli Zaretskii
2013-01-16 0:04 ` Richard Stallman
2013-01-23 0:40 ` Mark Lillibridge
2013-01-15 17:29 ` Glenn Morris
2013-01-16 0:04 ` Richard Stallman
2013-01-16 1:14 ` Glenn Morris
2013-01-17 6:26 ` Mark Lillibridge
2013-01-17 21:04 ` Richard Stallman
2013-04-01 19:06 ` Mark Lillibridge
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=83obgygtwc.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=mark.lillibridge@hp.com \
--cc=rms@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).