Harri, I have read your Usenet stuff and believe it or not, I have undertood it! :-) It would seem that not ALL UNIX-based documents are of a sybillic nature. Anyway what I didn't understand is what I am supposed to do exactly. From your note I conclude you are trying to set up a gateway to your UNIX usenet system, but will the gateway be LISTSERV or some other server? What do I have to do exactly? My impression was that a USENET mail header format was required with the following differences from the present FULLHDR: - Create a Message-ID: if not present. - Create a Path: if not present, otherwise append info to it. - Place the listname in the Netnews: tag. I'd like all potential USENET gatewayers to agree on what is needed before I start doing anything. Thomas Habernoll was also working on a similar gateway. About files: this is a very difficult point. Let's write a good mail interface before we start playing with files. You have the file format problem, and above all the header problem. As soon as the file enters the DISTRIBUTE processor, the "source list" info is lost (worse: you don't even know which LISTSERV is going to ship the file to you). But the mail envelope must be generated by the server that does the actual sending, ie within the DISTRIBUTE processor. Problem :-( Geez, I've just found out that the Crosswell mailer does not support fields like: To: ERIC@FRECP11, LISTSERV owners: HAROLD@UGA, JEFF@UTCVM;, LSTSRV-L@FRECP11 And I've also found to my dismay that any Joe user can send mail from any network address to anybody in the network using Crosswell. I'm starting to like the product more and more... *sigh* If RFC822 was not so shitty I would have proposed to create a new tag, 'NJE-From: userid node', which would have solved all those problems, but... Oh well. Eric