Received: from localhost by CS.UTK.EDU with SMTP (cf v2.9s-UTK) id NAA25754; Mon, 18 Sep 1995 13:39:40 -0400 X-Resent-To: drums@CS.UTK.EDU ; Mon, 18 Sep 1995 13:39:38 EDT Errors-to: owner-drums@CS.UTK.EDU Received: from Tomobiki-Cho.CAC.Washington.EDU by CS.UTK.EDU with SMTP (cf v2.9s-UTK) id NAA25739; Mon, 18 Sep 1995 13:39:30 -0400 Received: from UW-Gateway.Panda.COM by Tomobiki-Cho.CAC.Washington.EDU (5.65+UW95.02/UW-NDC Revision: 2.27.MRC ) id AA08135; Mon, 18 Sep 95 10:39:18 -0700 Received: from localhost by Ikkoku-Kan.Panda.COM (NX5.67e/UW-NDC/Panda Revision: 2.27.MRC ) id AA17625; Mon, 18 Sep 95 10:39:07 -0700 Date: Mon, 18 Sep 1995 10:37:50 -0700 (PDT) From: Mark Crispin Sender: Mark Crispin Subject: Re: Resent- facility To: Harald.T.Alvestrand@uninett.no Cc: Jacob Palme , Keith Moore , ietf-drums In-Reply-To: <199509181255.IAA28208@CS.UTK.EDU> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII On Mon, 18 Sep 1995 14:55:00 +0200, Harald.T.Alvestrand@uninett.no wrote: > I've found Resent: useful in one single instance: > > When a message is in my mailbox, and should have been in the mailbox > of an automatic processor, I want to forward it, but make it appear > as if it came from the original sender. This is precisely why ReSent (or Remailed or Redistributed in its earlier incarnations) exists, and precisely why those of us who use it do not want to see egregious changes made to it. This is a useful function which we emphatically do not want to lose. MIME forwarding is *not* a replacement for this function.