Date: Wed, 4 Oct 95 00:29:13 -0500
From: Eric Norman <ejnorman@macc.wisc.edu>
Reply-To: drums@CS.UTK.EDU
Message-Id: <9510040529.AA14571@dogie.macc.wisc.edu>
To: drums@CS.UTK.EDU
Subject: Re: What's the sender header for?

>> Keith says that there's no clear interface 'tween RFC822 and RFC821.
>> In light of the above paragraph, I'm going to lightheartedly disagree
>> and say that there is too.  The interface says that they're independent

>What's not completely clear is how you generate an SMTP envelope 
>if you start with an RFC 822 message (For instance, how do you
>handle Bcc headers?

I see your point and retract my disagreement.

I think that CC: headers are supposed to convey the notion
"for you information", which means to me that such folks are
not expected to participate in any discussions.  Why would
they expect to see replies?  Even more so for Bcc: recipients;
no one is supposed to know they're eavesdropping.

I'm not arguing for anything here as much as I'm asking questions.
If we have To: CC: and Bcc: headers for recipients, they must
have different meanings, otherwise why have them?  What exactly are
those meanings?  What ramifications do those differences have as far
as replying to a message goes?

I realize that you often want a reply to go to "everyone that
saw this message" (like this one).  But that doesn't  necessarily
mean to me that a UA should ferret out all the To: CC:, etc.
addresses and send replies there; it might mean that the message
was improperly composed.

A big question is, "Who decides where the replies to a message
should normally go?"  It's probably better to word it, "Who makes
the first suggestion about where replies should go?", since the
replier always has the final say.

>And more to the point, where does MAIL
>FROM come from?  Do you generate it from the Sender field?)

Any reason it doesn't come from the same place it would come from
if you were just creating and sending a message?  The only case I
can think of when you would need to generate it from RFC822 headers
is if the message is being gatewayed from a non-SMTP envirinment,
in which case we're going to say get it from the Return-Path: header,
right?

-- Eric Norman