jeff@questar.QUESTAR.MN.ORG (Jeff Holmes) (11/25/89)
Could someone who has installed smail on Xenix 2.3.2 (386) email some tips on installation? The part that confuses me is in the Install instructions. The instructions specify which NEW files go where and which OLD files go where, but the paths aren't the same for Xenix as in vanilla SYSV. ie. Xenix sports a /bin/Mail and a /usr/bin/mail but Install says to move /bin/mail to /bin/lmail. Does this mean mv /usr/bin/mail to /usr/bin/lmail? Below are the instructions could someone insert the meaning as it applies to Xenix? (after compiling smail) 1. cp smail /bin/smail (no problem) 2. mv /bin/mail /bin/lmail (???) 3. mv svbinmail /bin/mail (no problem) 4. mv /bin/rmail /bin/OLDrmail (???) 5. ln /bin/smail /bin/rmail (no problem) Thanks, much appreciation! Jeff -- Jeff Holmes DOMAIN: jeff@questar.mn.org Questar Data Systems UUCP: amdahl!bungia!questar!jeff St. Paul, MN 55121 AT&T: +1 612 688 0089
chip@vector.Dallas.TX.US (Chip Rosenthal) (11/26/89)
In article <4043@questar.QUESTAR.MN.ORG> jeff@questar.UUCP (Jeff Holmes) writes: > The part that confuses me is in the Install instructions. Throw the instructions in the crapper. They are useless. The XENIX mail configuration is totally different. The whole key is that under XENIX, the mailing is done by /usr/lib/mail/execmail. At least it is once you've entered "set execmail" in your /usr/lib/mailrc (which you *do* want to do for this). From there there are two choices: 1) Install a fake "execmail" which redirects the message into smail. There are some patches in the comp.sources.misc archives which make smail work with xenix and include the fake execmail. Be careful, there are several revs in the archives. Get the latest. 2) My preference is to patch smail that it may be installed as /usr/lib/mail/execmail. You can then throw execmail in the crapper with the smail installation instructions. :-) However, with this approach you lose Micnet support (yawn). I'd be glad to send out a copy of this patch. -- Chip Rosenthal /// chip@chinacat.Lonestar.ORG /// texbell!chinacat!chip ===> By the time you receive this, <chip@vector> will be inactive. ===> Please send replies to <chip@chinacat>.
jim@bahamut.fsc.com (James O'Connor) (11/26/89)
In article <1122@vector.Dallas.TX.US>, chip@vector.Dallas.TX.US (Chip Rosenthal) writes: > are some patches in the comp.sources.misc archives which make smail > work with xenix and include the fake execmail. Be careful, there are > several revs in the archives. Get the latest. Or you could write to chip@ateng.com to get the latest version, since he is the author. > 2) My preference is to patch smail that it may be installed as > /usr/lib/mail/execmail. You can then throw execmail in the crapper > with the smail installation instructions. :-) However, with this > approach you lose Micnet support (yawn). I'd be glad to send out a > copy of this patch. You don't necessarily loose Micnet support by replacing execmail. The basic scheme of smail2.5 is that you have either local mail (delivered by the command specified by the LMAIL macro) or remote mail (delivered by the command specified by the RMAIL macro). If you want to replace execmail with smail2.5, or have mail addressed like user@machine or machine!user delivered via smail2.5 over micnet connections, then you can use a program in the RMAIL macro that figures out, according to the host name, whether to use Micnet, uucp, or whatever, to deliver the mail. If anyone's interested, I have a quick little hack which does this. ------------- James B. O'Connor Work: jim@tiamat.fsc.com Filtration Sciences -- Play: jim@bahamut.fsc.com A division of Ahlstrom UUCP: uunet!tiamat!jim