Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!husc6!hao!boulder!forys
From: forys@sigi.Colorado.EDU (Jeff Forys)
Newsgroups: comp.bugs.4bsd
Subject: Re: CCA Emacs bogosity (really /usr/ucb/Mail)
Message-ID: <1496@sigi.Colorado.EDU>
Date: Wed, 1-Jul-87 20:34:13 EDT
Article-I.D.: sigi.1496
Posted: Wed Jul  1 20:34:13 1987
Date-Received: Fri, 3-Jul-87 02:19:21 EDT
References: <5750@think.UUCP> <2350@hoptoad.uucp>
Reply-To: forys@boulder.Colorado.EDU (Jeff Forys)
Distribution: world
Organization: University of Colorado, Boulder
Lines: 20

In article <2350@hoptoad.uucp> gnu@hoptoad.uucp (John Gilmore) writes:
> I end up running /bin/mail all the time because it will let me type:
>	% mail user
>	Subject: this
>	Bcc: me

Using /bin/mail to get an automatic `Bcc:' line is a little extreme.
You can use `~h' to edit "Bcc" and a couple other header fields.
It uses the infamous TIOCSTI ioctl (where available).  'Course, you
cant add any new `clever' headers.  It may have been done that way
for simplicity, or `security' :-) ...

> ...so if somebody is really considering fixing Berkeley Mail, how
> about fixing the whole problem rather than applying another patch?

Why bother?  There are other, far superior mail interfaces out there.
You might try `mh', it's extremely flexible (i.e. configurable).  Uh,
but if you dont have the time to learn a new mail interface...  :-)
---
Jeff Forys @ UC/Boulder Engineering Research Comp Cntr (303-492-4991)
forys@Boulder.Colorado.EDU  -or-  ..!{hao|nbires}!boulder!forys