Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!think.com!zaphod.mps.ohio-state.edu!wuarchive!uunet!pdn!palan!sherpa!rac
From: rac@sherpa.UUCP (Roger Cornelius)
Newsgroups: comp.mail.mush
Subject: SCO UNIX and MMDF (Was: Patch #3 for Mush 7.2)
Message-ID: <596@sherpa.UUCP>
Date: 24 May 91 16:10:50 GMT
References: <9105230730.AA19087@cse.ogi.edu>
Organization: Personal System Computing,  St. Petersburg, FL
Lines: 33

In the recently posted mush patch #3 for 7.2:

>   * SCO UNIX 3.2 users who are having problems with "submit" can now
>     define M_EXECMAIL to use execmail as their interface to MMDF.  This
>     has the pleasant side-effect of making the MTA invocation compatible
>     with sendmail, so resetting the variable "sendmail" works cleanly.

[...]

> +     If you are using SCO UNIX 3.2 and the MMDF "submit" program gives you
> +     trouble because of file permissions, define M_EXECMAIL to use the
> +     execmail program instead.


Why should this require a patch to mush?  If you're using SCO UNIX
and the MMDF "submit" program gives you trouble because of file
permissions, then shouldn't you fix MMDF's file permissions.  The
solution has been posted several times to various groups.

cd /usr/mmdf
su mmdf -c "./checkup -p" 2>&1 | more
follow the recommendations it makes

I've been using mush on SCO UNIX (first 3.2.0, now 3.2.2) since
February 90, and have always used "submit".  Other than the "sendmail"
variable stuff, I see no reason for this part of the patch.  Instead,
why not include instructions with mush for fixing MMDF's permissions
on SCO UNIX.

--
Roger Cornelius          rac@sherpa.UUCP         uunet!sherpa!rac