As a sendmail security measure, majordomo compiles it's uid:gid into the wrapper
program. Did you keep these the same when you moved to a different host? Did
you maintain "identical" directory heirarchy? Does DNS know about the domain
change? MX records? Did you bring the aliases file to the new host, or at least
the aliases related to majordomo mailing lists? Did you retain file/directory
ownerships and permissions? Did you tell sendmail on the new machine to "trust"
the majordomo user? Did you create a link to majordomo's wrapper in the
/var/adm/sm.bin directory? (assuming this is the directory smrsh looks in)
If you are using a separate aliases file for majordomo lists, is that filename
listed in "O AliasFile=" in sendmail.cf?
Dan Liston
"Joel M. Fisher" wrote:
>
> Hey All,
>
> I'm in the process of moving our list server to another server which has a
> different hostname. During testing I'm having a heck of a time making majordomo
> send messages to listname@listmgr.domainname instead of listname@hostname.
> $whereami is set to listmgr.domainname. The current list server is working
> without a problem with a different domain name than hostname, but I can't find
> where the config difference may lie. I copied over the majordomo install from
> the production box and just added test in front of the domain name for test
> purposes.
>
> Moving from:
> Solaris 8
> Sendmail 8.9.3
>
> to:
> Solaris 8
> Sendmail 8.10.2
>
> Quite possibly the problem resides in the sendmail config, but I can't find it.
>
> Thanks in advance for any suggestions,
>
> Joel
References:
-
Domain name
From: "Joel M. Fisher" <jfisher@wfubmc.edu>
|
|
