Clayton McGow wrote:
>
> Hi,
>
> My copy of majordomo ran fine on our machine (several
> virtual domains + multiple IPs) until I changed the primary
> interface name from "raq7.atoznet.com" to "ns1.atoznet.com".
If you change the name back to raq7 does it start working again?
>
> I can still send email to the lists just fine, and they go
> through to the subscribed members. However, I am no longer
> able to send email to majordomo@atoznet.com, nor am I able
> to send email to majordomo@ns1.atoznet.com.
This means your listname-request addresses don't work either?
>
> If I telnet in as an administrator, I can type "echo
> 'help'|mail majordomo", but I cannot issue the same command
> if I telnet in as a normal user (I get a 550 error,
> nonPriviledgedUserName@ns1.atoznet.com - unknown user,
> presumably because these users can only be sent email at
> atoznet.com, NOT ns1.atoznet.com) .
Probably because majordomo is installed with admin ownerships
rather than majordomo ownerships. This could also mean that
the wrapper is using the wrong uid/gid too.
>
> I have these records, among others, in the dns settings:
> A atoznet.com -> 63.230.201.226
> A www.atoznet.com -> 63.230.201.226
> A ns1.atoznet.com -> 63.230.201.225
> P 63.230.201.225 -> ns1.atoznet.com
> P 63.230.201.226 -> www.atoznet.com
> M atoznet.com is sent High to atoznet.com
I have never seen any zone files that looked like the above.
What are you "really" saying? <G>
atoznet.com has an A record, but does it have an MX record that
points to ns1.atoznet.com? Perhaps this is the problem? Mail
is trying to go to the web server's IP and not getting to majordomo.
>
> and all the services on this box are working fine, including
> telnet, ftp, pop, imap, smtp, web, you name it.
I have my doubts about smtp unless both IP addresses are on the
same box.
>
> this line is in aliases.majordomo:
> majordomo: "|/usr/local/majordomo/wrapper majordomo"
This is as it should be, as long as it actually exists and has
the correct ownerships and permissions.
>
> these lines are in virtusertable (I've tried the remarked
> out ones, too):
> #majordomo@atoznet.com majordomo_site1
> #majordomo@www.atoznet.com majordomo_site1
> majordomo@atoznet.com majordomo
> majordomo@www.atoznet.com majordomo
If www.atoznet.com and atoznet.com are on the same physical
drive/machine as ns1.atoznet.com, why are you doing anything
in the virtusertable?
>
> this is the entire 'hosts' file:
> 127.0.0.1 localhost
> 63.230.201.225 ns1.atoznet.com # main interface
OK, is .226 in the same box or not?
>
> running config-test reports no problems, here are what seem
> to be the most interesting lines:
> FQDN=ns1.atoznet.com
> LOGNAME=admin
> USER=admin
> --------------------- euid/egid checks ---------------------
> effective user = admin (uid 110)
> effective group = daemon wheel disk adm sys daemon bin
> root (gid 2 10 6 4 3 )
> ---------------------- uid/gid checks ----------------------
> real user = admin (uid 110)
> real group = daemon wheel disk adm sys daemon bin
> root (gid 2 10 6 4 3 )
> ------------------------------------------------------------
>
> The owner of every file in /usr/local/majordomo is "admin",
> except "wrapper", which is owned by root.
Why isn't everything owned and grouped by the majordomo user?
Is the majordomo user admin? BAD idea!
> The permissions appear to be okay, most things are set to
> 755 except the ones that end in "cf" or "pl"
Especially the .pl files should be 755. What the box renamed,
or was majordomo moved to this box?
>
> The log file contains many entries like these:
> Nov 28 00:26:56 atoznet.com majordomo[4465] {Clayton McGow
> <mrwilder@ns1.atozne$
> Nov 28 01:15:40 atoznet.com majordomo[5389] {Clayton McGow
> <mrwilder@ns1.atozne$
> Nov 28 01:45:30 atoznet.com majordomo[5765] {Administrator
> <admin@ns1.atoznet.c$
> Nov 28 01:50:48 atoznet.com majordomo[5825] {Clayton McGow
> <mrwilder@ns1.atozne$
> Nov 28 01:50:55 atoznet.com majordomo[5833] {Clayton McGow
> <mrwilder@ns1.atozne$
>
> Note that "mrwilder" is not a valid user at
> "ns1.atoznet.com", but he is a user at "atoznet.com". His
That is interesting, as majordomo logs who messages are "from:".
Why would it think the msg was from mrwilder@ns1 if that ID
does not exist?
> commands (which were issued during a telnet session) failed
> with 550- mrwilder@ns1.atoznet.com user unknown... the
> Administrator issued commands the same commands during a
> telnet session that succeeded (presumably because the UID is
> the same), but "admin" is a valid user at "ns1.atoznet.com"
> and a valid email adress at both domains.
>
> Dan Liston mentioned that my problems are probably more DNS
> and sendmail related than Majordomo itself. I believe this
> is true, and I notice specifically the fact that majordomo
> thinks it is at "ns1.atoznet.com" (63.230.201.225) but the
> mail server is at "atoznet.com" (63.230.201.226). As
> "atoznet.com" and "ns1.atoznet.com" are both fully qualified
> but seperate domains, I think this is probably related.
Go to the www machine and check for majordomo aliases and
the list aliases. Make sure messages to them are getting
directed to the ns1 box. The problem is not that you are
separating your web service from your dns service, but you
have inadvertantly separated your mail service from your
list service as well. Was this intended?
>
> And, to top it all off, I've ran newaliases and rebooted a
> coupla' hundred times.
But have you done this on both the .225 and .226 machines?
Do both machines accept mail as atoznet.com? Does one know
that the lists are on the other, and the list server majordomo?
>
> I'm sure there is enough information in this letter for some
> kid to hack in and bring the whole server to the ground, uh,
> is there anything that stands out as "obviously messed up"
> for one of you "wise men" or "wise women" out there?
Putting in grueling 16-18 hour days in Utah. Will try to catch
up again this weekend.
Dan Liston
References:
|
|
