Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uwm.edu!psuvax1!psuvm!PUCC!MAINTCMS From: MAINTCMS@PUCC.BITNET (John Wagner) Newsgroups: bit.listserv.mailbook Subject: Re: BSMTP header Message-ID: Date: 7 Feb 90 19:38:27 GMT Sender: MAIL/MAILBOOK subscription list Reply-To: MAIL/MAILBOOK subscription list Lines: 24 Approved: NETNEWS@PSUVM Gateway In-Reply-To: Message of Wed, 7 Feb 90 13:05:05 SET from Christian, I have been working on a fix for handling VNET better. I'd be interested in your (and other folks) comments as to what is generally useful. Here's my assumptions: 1. VNET mail is recognized by the origin node of VNET (in the tag at the receiver's end) 2. The nickname id (i.e. the userid you must specify when sending the file to the VNET gateway) is given as the userid in the tag I am making several modifications, but I'll use the case of a PROFS file as an example. Once the mail file is recognized as being in PROFS format, the MAILPROF routine is called to reformat the headers into RFC822 conformance (we hope). If the file is from VNET, I now pass the correct userid (nickname@VNET taken from the tag) to use in the From: line (I should also have MAILPROF put in a comment for the real userid and node inside VNET, but I haven't done that yet). This allows the MAILPROF exit to properly reformat and rebuild the headers. Similar processing must be done for NOTE format files and replacement of the From: line must be done in RFC822 mail (I wish they would all use PROFS and make it easy). Is there anything else I should be doing?