From: Richard M Stallman <rms@gnu.org>
To: Harald Hanche-Olsen <hanche@math.ntnu.no>
Cc: emacs-devel@gnu.org
Subject: Re: Change in rmail-reply
Date: Thu, 29 Jan 2009 09:32:18 -0500 [thread overview]
Message-ID: <E1LSXwI-0001L6-7L@fencepost.gnu.org> (raw)
In-Reply-To: <20090128.002236.153267880.hanche@math.ntnu.no> (message from Harald Hanche-Olsen on Wed, 28 Jan 2009 00:22:36 +0100 (CET))
Note: Reintroducing a message into the transport system and using
resent fields is a different operation from "forwarding".
"Forwarding" has two meanings: One sense of forwarding is that a mail
reading program can be told by a user to forward a copy of a message
to another person, making the forwarded message the body of the new
message. A forwarded message in this sense does not appear to have
come from the original sender, but is an entirely new message from
the forwarder of the message.
Now I understand how these terms are being used. Forwarding and
resending do similar jobs, but package the message differently.
The RFC is clear, but it seems to be clearly wrong. If John Doe sends
a message to you, and you resend it to me, and I do "reply to all", it
seems clear that my reply should by default go to and to all the
other people you resent it to -- as well as to the sender and recipients
of the original message.
Can anyone present an argument in support of what the RFC says?
Someone else wrote:
The distinction is the difference between "I'd like you to see this
mail" and "this mail was misdirected to me". [If you've used mutt,
it's the difference between forward and bounce.]
I can see why, in the misdirected case, you would prefer to use resend.
I have not seen any statement previously that resend is only intended
for that case. Is this the stated purpose of resend?
But if that is the motive for using resend, it seems to support
the conclusion that replies should go to the other people
to whom you resent the message.
next prev parent reply other threads:[~2009-01-29 14:32 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-26 16:30 Change in rmail-reply Richard M Stallman
2009-01-26 17:39 ` Glenn Morris
2009-01-27 6:10 ` Richard M Stallman
2009-01-27 6:44 ` Don Armstrong
2009-01-27 18:18 ` Stefan Monnier
2009-01-27 22:58 ` Richard M Stallman
2009-01-27 23:22 ` Harald Hanche-Olsen
2009-01-29 14:32 ` Richard M Stallman [this message]
2009-01-29 15:08 ` Stefan Monnier
2009-01-29 16:36 ` Stephen J. Turnbull
2009-01-30 7:25 ` Richard M Stallman
2009-01-30 8:04 ` Stephen J. Turnbull
2009-01-30 23:05 ` Richard M Stallman
2009-01-31 0:50 ` Chetan Pandya
2009-01-31 1:01 ` Chetan Pandya
2009-01-31 3:16 ` Jason Rumney
2009-01-31 3:53 ` Chetan Pandya
2009-01-31 6:32 ` Stephen J. Turnbull
2009-01-31 9:52 ` Chetan Pandya
2009-02-01 6:30 ` Richard M Stallman
2009-01-31 3:18 ` Jason Rumney
2009-01-31 3:31 ` Jason Rumney
2009-02-01 6:30 ` Richard M Stallman
2009-01-31 4:57 ` Stephen J. Turnbull
2009-01-27 23:35 ` Don Armstrong
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E1LSXwI-0001L6-7L@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=hanche@math.ntnu.no \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.