Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 6/24/83; site hou3c.UUCP
Path: utzoo!watmath!clyde!burl!hou3c!MRC@SU-SCORE.ARPA
From: MRC@SU-SCORE.ARPA (Mark Crispin)
Newsgroups: net.mail.headers
Subject: user-editable headers
Message-ID: <768@hou3c.UUCP>
Date: Tue, 21-Aug-84 11:27:06 EDT
Article-I.D.: hou3c.768
Posted: Tue Aug 21 11:27:06 1984
Date-Received: Fri, 24-Aug-84 04:08:16 EDT
Sender: ka@hou3c.UUCP (Kenneth Almquist)
Reply-To: MRC@SU-SCORE.ARPA
Lines: 17
To: Header-People@MIT-MC.ARPA
Postal: Systems Concepts; 520 Third Street; San Francisco, CA 94107
Phone: (415) 442-1500 x31


     The main objection I have to the idea of popping you into an
editor to compose the message and then parsing the header to see
where the message goes to is that there is not necessarily a
correspondence between the header of a message and its envelope!
Just about every mail system (including TOPS-20's MM) I am aware
of which has this capability has this fundamental flaw.

     The problem is what you do about things which do not conform
to the definition of 822 but are still valid under it.  The best
example I can think of is the tradition of using group names to
hide a recipient list (this is the original usage of group names
from long long ago and, I imagine, still its primary usage).
bcc's present another problem; there are several theories on the
correct bcc behavior which can only be determined at mailer
instead of editor level.
-------