Received: from localhost by CS.UTK.EDU with SMTP (cf v2.9s-UTK)
	id XAA25021; Tue, 3 Oct 1995 23:10:17 -0400
Received: from wilma.cs.utk.edu by CS.UTK.EDU with ESMTP (cf v2.9s-UTK)
	id XAA25008; Tue, 3 Oct 1995 23:10:14 -0400
Received: from LOCALHOST by wilma.cs.utk.edu with SMTP (cf v2.11c-UTK)
          id XAA26720; Tue, 3 Oct 1995 23:10:13 -0400
Message-Id: <199510040310.XAA26720@wilma.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@CS.UTK.EDU>
To: Eric Thomas <ERIC@SEARN.SUNET.SE>
cc: drums@CS.UTK.EDU, Eric Norman <ejnorman@macc.wisc.edu>, moore@CS.UTK.EDU
Subject: Re: What's the Sender header for? 
In-reply-to: Your message of "Wed, 04 Oct 1995 02:43:43 BST."
             <199510040155.VAA18225@CS.UTK.EDU> 
Date: Tue, 03 Oct 1995 23:10:06 -0400
Sender: moore@CS.UTK.EDU

> >Furthermore,  RFC822 specifically  says (4.4.4)  that the  Sender: field
> >should  be sent  notices of  non-delivery, etc. 
> 
> Actually, I'd  like to put in  a motion that we  deprecate this. Nowadays
> there seems to be a pretty clear agreement that in a SMTP environment you
> MUST use MAIL FROM:<>, and  that in a non-SMTP environment "Return-Path:"
> is your best bet.

I second the motion.  Actually, I think this is pretty clear from RFC 1123,
so we just need to clean up the text in the revised 822.  

Keith