From: "Stephen J. Turnbull" <stephen@xemacs.org>
To: rms@gnu.org
Cc: emacs-devel@gnu.org
Subject: Re: Change in rmail-reply
Date: Sat, 31 Jan 2009 13:57:35 +0900 [thread overview]
Message-ID: <87ab98cbsw.fsf@xemacs.org> (raw)
In-Reply-To: <E1LT2QK-0006el-65@fencepost.gnu.org>
Richard M Stallman writes:
> > As for fowarding, that is no substitute, since the new header does not
> > include the sender or other recipients of the original message. When
> > you want to exclude them, forwarding is suitable. Otherwise, it isn't.
>
> That's an issue with your MUA, if that is a common use case for you.
>
> I do not follow. What issue about the MUA are you raising?
The need for a rmail-resend variant which allows editing the headers,
as you describe below. Personally, I would tend to add the feature to
the forward command instead, but thats a matter of style, not substance.
> > Should we delete the rmail-resend command?
>
> No. Better to rename it to something like rmail-bounce.
>
> "Bounce" in the context of mail usually indicates report that a
> message failed to reach a recipient. Does this case have anything to
> do with such a failure? If not, what's the reason to suggest
> using that word?
The analogy is that physically, something that bounces doesn't
interact with the thing in bounced off of; it simply changes
direction, leaving both the bouncer and the bouncee otherwise
unchanged. The failed-mail report originally was a special case of
this, with just enough additional information to identify it clearly
as a resend for the purpose of identifying an error. Thus it is
called a "bounce". The semantics have changed, but the name stuck.
> It occurs to me that maybe there should be two resend commands:
> one which lets you edit the message and one which doesn't.
> The former would be new. It could insert CC commands
> with the resend recipients, so you can either keep them or
> delete them.
As long as there is no parsing of Resent-* headers for addresses to
add to the recipient list, that would be fine.
Note that the semantics of mail for this purpose are still
problematic. The original recipients may never know that the
conversation has been broadened in this way if you don't send the
forward (with the new headers) to them, too. On the other hand, they
might not care, and be annoyed by the duplication. It's not a big
hairy deal, of course, but these nuances apparently matter somewhat to
you. To the extent that they do, you may wish to advocate changing
the channels where you want to use these features to use more
appropriate technology (usenet, web forum, etc).
next prev parent reply other threads:[~2009-01-31 4:57 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
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 [this message]
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=87ab98cbsw.fsf@xemacs.org \
--to=stephen@xemacs.org \
--cc=emacs-devel@gnu.org \
--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 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.