Errors-to: owner-drums@CS.UTK.EDU
To: Keith Moore <moore@CS.UTK.EDU>
Cc: Dave Barr <barr@math.psu.edu>, drums@CS.UTK.EDU
Subject: Re: getting started 
In-Reply-To: Your message of "Wed, 31 May 1995 15:36:21 -0400."
             <199505311936.PAA12316@wilma.cs.utk.edu> 
Date: Thu, 01 Jun 1995 06:01:02 +1000
Message-Id: <824.801950462@munnari.OZ.AU>
From: Robert Elz <kre@munnari.oz.au>

    Date:        Wed, 31 May 1995 15:36:21 -0400
    From:        Keith Moore <moore@CS.UTK.EDU>
    Message-ID:  <199505311936.PAA12316@wilma.cs.utk.edu>

    > 2. When a person activates the "reply" function of their MUA, what addresses
    >    should go in the header?

    Given our charter, I wonder how much we can specify of UA
    functionality.  822 specifies how a UA should address replies, so I
    guess we can clarify that much.

Along the same lines, and without being certain whether this
is a cleanup, or new functionality in some sense or other, there
badly needs, sometime, to be some kind of specification as to
what all the Resent-* headers really mean, how and when they're
used, etc.   That includes whether or not they should be used
when sending replies, whether there is a Resent-Reply-To, ...
    
    The 822 extension model tacitly assumes that since everything in the
    header is for the benefit of the recipient's user agent, nothing you
    put in a header should be able to affect transport or delivery.  This
    needs to be stated explicitly.

I doubt you really meant to say exactly that.   If you did,
this message wouldn't be able to get to you, as nothing would
be allowed to look in the To: header to figure out where I
intended to send it!

I think I understand what you really mean though, but strict
observance to this causes problems when messages are relayed
through gateways to other networks - you simply cannot count
upon SMTP, or anything like it, existing for 822 mail delivery.
There is no requirement that 822 mail use SMTP for delivery.

kre