🚀 go-pugleaf

Right.  If a message claims to come from the original sender, the
sender's original message body shouldn't be modified, only the header
(and only by the addition of the Resent headers).  Kyle, please keep
this pure!  I've got into trouble in the past replying to someone's
comments and having my reply go to the original sender who wasn't
supposed to know about the comments.

In article <9202202222.AA18291@thalidomide.lucid> Jamie Zawinski <jwz@lucid.com> writes:

   Newsgroups: gnu.emacs.vm.bug
   Sender: bug-vm-request@uunet.uu.net
   Date: Thu, 20 Feb 92 14:22:55 PST
   X-Windows: A moment of convenience, a lifetime of regret.
   From: Jamie Zawinski <jwz@lucid.com>
   References: <9202121811.AA03026@thalidomide.lucid>
	   <JBW.92Feb20154611@bigbird.bu.edu>
	   <9202202115.AA02605@wendy-fate.UU.NET>
   Path: newsstand.cit.cornell.edu!uunet!wendy-fate.uu.net!bug-vm

   In message <9202202115.AA02605@wendy-fate.UU.NET> kyle@wendy-fate.uu.net wrote:
   >
   > Why not just type your comment in at the top of the message, in
   > brackets or something.  The comments would be more likely to be
   > seen by users who have mailers that don't show alien headers.

   So you're suggesting that when I want to resend a message to someone, I first
   edit the message, and then resend it?  I don't like that very much because it
   means I'm editing *my* copy of the message as well as annotating the copy I'm
   going to send someone.  I don't want my original copy of the message altered
   just because I'm shipping it elsewhere.  Making "resend" leave you in a send-
   mail buffer really seems like the rational thing to do; it's also a more 
   consistent interface.  The first time I used "resend" I was very surprised
   that it just sent it off without any further confirmation; no other VM mail-
   sending command does that.

	   -- Jamie