Path: utzoo!attcan!uunet!cs.utexas.edu!usc!zaphod.mps.ohio-state.edu!van-bc!ubc-cs!uw-beaver!sumax!amc-gw!thebes!happym!rwing!nanook From: nanook@rwing.UUCP (Robert Dinse) Newsgroups: comp.mail.uucp Subject: Re: Xenix Mail Summary: Thought I needed to be more specific about my request. Keywords: Xenix, Mail, Tandy Message-ID: <105@rwing.UUCP> Date: 26 Jun 90 23:52:51 GMT References: <102@rwing.UUCP> <4701@thebes.Thalatta.COM> Organization: Totally Unorganized Lines: 29 > Chip Salzenberg has developed a set of patches for smail that > work beautifully with Xenix. I can e-mail if you want. > > Bill. > -- > ....microsoft--\ Bill Campbell; Celestial Software > ...uw-entropy----!thebes!camco!bill 6641 East Mercer Way > ....fluke------/ Mercer Island, Wa 98040 > ....hplsla----/ (206) 232-4164 Several people already mailed me those patches, and I appreciate that. But I'm really trying to gain a good understanding of how the mail delivery works. I'm trying to write some gateway software and would like to include some other facilities to interface with my software (Eskimo North). It's difficult to do that without having a good understanding of how the existing system works. Please don't take this as >I don't appreciate the offer<, I do, but I managed to get smail function some months ago. Now I am trying to figure out a way to implement a gateway to a local network. I might be able to gleem the information I need by studying the patches, but if someone actually understands it, it would make life easier. I am a little hesistant to use those patches anyway because they require execmail be set to work properly. I don't have it set because I occasionally use mail to mass mail users on my system of impending expirations or expected downtime or whatever. If you set execmail, it bombs as soon as you reach the per-user process limit and bogs the system, otherwise it just quietly chugs through the list.