Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!umich!samsung!brutus.cs.uiuc.edu!psuvax1!psuvm!HDEDH1!NADWL From: NADWL@HDEDH1.BITNET (Scott Ophof) Newsgroups: bit.listserv.mailbook Subject: Re: BSMTP header Message-ID: Date: 5 Feb 90 15:08:39 GMT Sender: MAIL/MAILBOOK subscription list Reply-To: MAIL/MAILBOOK subscription list Lines: 27 Approved: NETNEWS@PSUVM Gateway In-Reply-To: Message of Fri, 2 Feb 90 15:22:06 CST from On Fri, 2 Feb 90 15:22:06 CST Richard A. Schafer said: >>>... >... >It occurs to me that maybe we're really barking up an entirely wrong >tree here. Do we really want to have to depend on people entering >the exact syntax of an RFC822 address by hand? (Don't forget to >... My general feeling is that where users could "botch up" the header, I'd prefer that line to be a RESERVED one, which of course means possible extra commands to effect changes. And elsewhere I wouldn't mind being rapped on the knuckles at SEND-time. By the way, I even get the "changes may make header ...{reminder when I type a prefix command on one of the header lines which does NOT affect the header at all! >Maybe what we really need is a completely different way of looking at >the entire problem that allows full-screen changes, sure, but in >a less syntactically painful way. This will require a lot of thought >... Yes. Regards. Scott/