Re: config-test failed

[Ed Kasky <ed @ wrenkasky . com>]

This is an interesting one.  I checked all the paths to the wrapper and 
there are no world writable directories anywhere...

lrwxrwxrwx    1 root     root           28 Aug 28 22:23 wrapper -> 
/usr/local/majordomo/wrapper
-rwsr-xr-x    1 root     majordom    16847 Aug 28 17:34 
/usr/local/majordomo/wrapper

So I did a little test and put a link to rdate in /etc/smrsh and ran
# /usr/sbin/smrsh -c /etc/smrsh/rdate

and got the same results...

/usr/sbin/smrsh: rdate not available for sendmail programs

So I went digging in the sendmail faq:

"The default location of this directory for restricted programs is 
/usr/adm/sm.bin in the Open Source version, but vendor versions differ. For 
example, RedHat Linux 6.0 uses /etc/smrsh, and Solaris 8 uses 
/var/adm/sm.bin . If you don't know the directory for your OS, first check 
the smrsh man page, then if that fails, try:
         % strings /path/to/smrsh | grep ^/"

On my system (which I compiled from source) it returned

/lib/ld-linux.so.2
/usr/adm/sm.bin
/bin:/usr/bin:/usr/ucb
/bin/sh

So I made the link in /usr/adm/sm.bin and viola!!!!

Ed
~~
At 04:53 PM Thursday, 8/29/2002, Daniel Liston wrote -=>

>Well, if your majordomo configuration/installation is complete, and you
>know it to be correct, perhaps you should examine sendmail and it's .cf
>and .mc files?  Is your majordomo uid:gid the same as you used to compile
>the wrapper?  Are there any group or world writable directories in the
>path to wrapper (or the link)?  This includes /, /etc, and /etc/smrsh.
>Is wrapper suid root?
>
>Dan Liston
>
>Ed Kasky wrote:
>>Hey Dan -
>>I don't know if my last post got through but I finally deleted all the 
>>source files I had from a while back and dl'd a new tar from greatcircle 
>>and got it to work fine.  For some reason, it was not picking up the 
>>changes in Makefile and from the majordomo.cf I created...
>>Now if I can only figure out why, even after I have created a symbolic 
>>link to wrapper in /etc/smrsh and made majordomo a sendmail trusted user, 
>>restarted sendmail I am still getting:
>>"smrsh: wrapper not available for sendmail programs
>>554 5.0.0 Service unavailable"
>>when testing the install with "echo 'lists' | mail majordomo"
>>I have seen this countless times on this list and know that creating the 
>>symbolic link fixes it.
>>I have never had so many problems setting up a server as this go-round :-(
>>Ed
>>At 04:19 AM Thursday, 8/29/2002, Daniel Liston wrote -=>
>>
>>>It might be because that is also the default $home in the sample.cf and
>>>majordomo.cf file.  Just a guess at this point.  You did make a majordomo.cf
>>>before trying to run config-test right? :)
>>>
>>>>> > > > W_HOME = /usr/local/majordomo
>>>>> > > > W_MAJORDOMO_CF = $(W_HOME)/majordomo.cf
>>>>> > > >
>>>>> > > > And why is it looking in /usr/test/majordomo-1.94.5 anyway??
>>>>> > >
>>>>> > >It's looking in /usr/test/majordomo-1.94.5 because that's the default
>>>>> > >Majordomo home directory ($W_HOME) defined in the Makefile.
>>>>> >
>>>>> > I changed line 23 before running ./configure to "W_HOME =
>>>>> > /usr/local/majordomo" which is where I like to put majordomo.
>>>>>
>>>>>Weird.  Run 'strings' on the 'wrapper' binary, that'll show you whether
>>>>>your new path got into the binary at all.
>>>>
>>>>
>>>>  From the stdout of "strings wrapper"
>>>>MAJORDOMO_CF=/usr/test/majordomo-1.94.5/majordomo.cf
>>>>SHELL=/bin/sh
>>>>PATH=/bin:/usr/bin:/usr/ucb
>>>>HOME=/usr/test/majordomo-1.94.5
>>>>Which are directly from the sample.cf and not from the majordomo.cf and 
>>>>Makefile in the src folder...
>>>>
>>>>>My 1.94.5 distribution didn't come with a ./configure script, where did
>>>>>you get yours from?  If someone has GNU'ified the build procedure then
>>>>
>>>>
>>>>I dl'd it straight from greatcircle.com.   And it doesn't come with a 
>>>>configure script.  Install directions are really straight forward which 
>>>>is why I am sort of baffled as to how the wrapper keeps picking up 
>>>>these settings...
>