Was the OS upgraded "in place" on the same hardware? Were the user's
uid:gid maintained in the process? The wrapper has information
compiled in during install with dependencies on the numeric information
for uid:gid. If these number were not preserved, the wrapper will have
to be recompiled with the new information.
Did the new OS preserve sendmail's smrsh (if used) and in the same
location? Did the smrsh "work" directory change? Is the "real"
wrapper still suid to root?
Dan Liston
RJ.Dial@ual.com wrote:
> Arrggg!
> I get Majordomo 1.94.5 sweetly running with all it's features fully
> functioning and error free - and the server host compnay upgraded us
> last night from UNIX FreeBSD v4.1.1 to v4.4, and now every post and
> command to majordomo results in the following:
> -----------------------------------
> The original message was received at Wed, 4 Dec 2002 05:00:02 -0800
> (PST)
> from root@localhost
>
> ----- The following addresses had permanent fatal errors -----
> "|/usr/local/majordomo/wrapper majordomo"
> (reason: 255)
> (expanded from: majordomo)
>
> ----- Transcript of session follows -----
> Message delivered to mailing list majordomo
> Config file "/usr/local/majordomo/majordomo.cf" not owned by effective
> UID.
> 554 5.3.0 unknown mailer error 255
> -------------------------------------------
>
> The above noted files look like this:
> -rw-r--r-- 1 majordom majordom 10491 Oct 30 17:42 majordomo.cf
> -rwxr-xr-x 1 majordom majordom 62417 Nov 5 18:51 majordomo
> lrwxr-xr-x 1 root wheel 68 Dec 3 07:34 wrapper ->
> /usr/virtual/share/pkgs/installed/majordomo/1.94.5/majordomo/wrapper
>
> But I have the feeling that isn't the problem, because that's the way
> it's always been.
>
> Any ideas?
>
> RJ
> Airstream.org
Follow-Ups:
References:
|
|
