Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uwm.edu!uakari.primate.wisc.edu!brutus.cs.uiuc.edu!psuvax1!psuvm!ETSU!CMS2
From: CMS2@ETSU.BITNET (Bill Williams)
Newsgroups: bit.listserv.mailbook
Subject: Re: Proposals for yet another version of MAIL/BOOK
Message-ID: <MAILBOOK%90011815194450@UGA.BITNET>
Date: 18 Jan 90 19:55:36 GMT
Sender: MAIL/MAILBOOK subscription list <MAILBOOK@RICEVM1>
Reply-To: MAIL/MAILBOOK subscription list <MAILBOOK@RICEVM1>
Lines: 43
Approved: NETNEWS@PSUVM Gateway
In-Reply-To:  Message of Wed, 17 Jan 90 09:32:22 ECT from <AS0JEB@BINGVMA>

On Wed, 17 Jan 90 09:32:22 ECT Jim Blake said:
>>5. Editing the header part
>>   This topic  has already been discussed  here, but I'd like  to add my
>>   two cents:  Since I'm working  in a fullscreen environment,  I'd like
>>   to  make changes  to  the  subject line  by  simply  typing over  it,
>>   without having  to use a  (line mode) SUBJECT command.  Similarly I'd
>>...
>Don't weaken, Richard. I do not want to hear the complaints from the
>unsavvy users who clobbered their headers.

I don't mind the BSMTP envelope idea, but I now *need* an option to do a
"temporary" CHECK.LOCAL.ID=NO for "just this mail item".

OR perhaps a 'pc: userid' like the cc: and bcc: options which indicates
a pseudo-id instead of the option to override the CHECK.LOCAL.ID.

It is necessary sometimes to MAIL to a pseudo local user -- for example:
    MAIL C_CLASS
where C_CLASS is not really a local userid but rather a LIST defined in
our MAILER (r2.05).

Yes, I can set my CHECK option to NO, do the MAIL and then set my CHECK
back to YES, but the main use of the MAILER LIST capability is for
(*gasp*) users.  Since users are the very ones with the expertise to
really trash the headers by editing them, they are the very ones I don't
want to be able to 'edit' the headers.  And they need to be watched over
in events where they are actually misspelling the name of the target and
ending up with a genuinely wrong destination; this means that they need
to do something deliberate in order to *know* that they're specifying a
pseudo user -- the list.

Or perhaps some special :tag.value in the names file for the given LIST
to tell MAIL that this user's Ok.  Maybe a :node. with non-valid node
name characters to indicate that this is a local pseudo user?

Any "easy to set up for the end user"  (we're talkin faculty, here)
method for using MAIL to talk to the MAILER defined LIST userid would be
helpful.  Or is the best thing to simply create dummy CMS userids for each
list-name in MAILER and just let the rough side drag?   :-)

BTW: I'm OCO for MAIL/MAILBOOK.
----------
    B.R.Wms