Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uwm.edu!zaphod.mps.ohio-state.edu!brutus.cs.uiuc.edu!wuarchive!psuvax1!psuvm!PUCC!MAINTCMS From: MAINTCMS@PUCC.BITNET (John Wagner) Newsgroups: bit.listserv.mailbook Subject: Re: BSMTP header Message-ID: Date: 2 Feb 90 18:24:41 GMT Sender: MAIL/MAILBOOK subscription list Reply-To: MAIL/MAILBOOK subscription list Lines: 18 Approved: NETNEWS@PSUVM Gateway In-Reply-To: Message of Fri, 2 Feb 90 12:34:41 LCL from On Fri, 2 Feb 90 12:34:41 LCL Michael Wagner said: > Besides, most header >manipulation I do can't be done with the supplied commands. I've found that in my job as postmaster this is a big problem for me, also. I expect that once the new MAIL/MAILBOOK goes into production here I will be setting up a separate id to do postmaster stuff simply because I can no longer modify the headers. The list of things I need supported are: Full RFC822 addresses (including route addresses) "!" addresses (we see a fair amount of UUCP traffic) EXCLUDE that works with the full address Excluding of ids from only one header line type (to: cc:, etc.) I used to be able to do this stuff by hand. For me the change to BSMTP was a step backward. This is not to say the code is bad, it simply doesn't fit my needs as well as it did before.