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!ALPERN%SJRLVM4.BITNET@Berkeley.ARPA From: ALPERN@SJRLVM4.BITNET (David Alpern) Newsgroups: net.mail.headers Subject: Re: user-editable headers Message-ID: <8408221732.AA23132@ucbjade.CC.Berkeley.ARPA> Date: Wed, 22-Aug-84 13:30:45 EDT Article-I.D.: hou3c.774 Posted: Wed Aug 22 13:30:45 1984 Date-Received: Fri, 24-Aug-84 04:34:36 EDT Sender: ka@hou3c.UUCP (Kenneth Almquist) Lines: 27 To: MRC@SU-SCORE.ARPA Cc: Header-People@MIT-MC.ARPA In-Reply-To: Message of Tue 21 Aug 84 08:27:06-PDT from Mark Crispin Both the problem of BCCs and of recipient lists can be dealt with reasonably by having the "header template" creator include all of the addressees (all members of the group, all BCC entries) in the header as seen within the editor, and then "hiding" the appropriate entries as the header is parsed to create the envelope. The only difficulty is how to separate those groups whose members the user wants seen from those whose recipient list is to be hidden. Our choice was to hide all group recipient lists, since people did not seem to be using any group names in situations where the recipient list was wanted. Another possibility would be a syntactic distinction (e.g. a * instead of a : after the group name) between the two uses. The only problem this seems to leave is that the user might edit a group recipient list which gets hidden, yielding misleading information about who the recipients were. Since group names really have no semantic meaning from a recipient's viewpoint anyhow, this seems mute. Is there a side to this problem I've missed? - Dave David Alpern IBM San Jose Research Laboratory, K65/282 5600 Cottle Road, San Jose, CA 95193 Phone: (408) 284-6521 Internet: Alpern%IBM-SJ@CSnet-Relay.ARPA Alpern@SJRLVM4.BITNET