Hello,
I am trying to setup a Majordomo list using Majordomo 1.94.4 running under
RedHat 6.0 and the following kernel:
Linux rmc1.crocker.com 2.2.10-ac2 #4 SMP Wed Jun 16 18:03:16 EDT 1999 i686
unknown
Incoming domain mail is sorted with a virtusertable located at
(204.97.12.2). The virtusertable looks as follows:
# wa1mba.org
microwave-outgoing@wa1mba.org microwave-outgoing@crocker.com
microwave-archive@wa1mba.org microwave-archive@crocker.com
microwave-approval@wa1mba.org microwave-approval@crocker.com
microwave-request@wa1mba.org microwave-request@crocker.com
microwave@wa1mba.org microwave@crocker.com
@wa1mba.org tomw@crocker.com
The mail is then sent to a (204.97.12.50) machine where the /etc/aliases
table will parse the @crocker.com addresses. Here are the aliases:
###
# Wa1mba
###
owner-microwave: tomw@crocker.com, nobody
microwave: "|/home/majordomo/wrapper resend -l microwave -h
rmc1.crocker.com microwave-outgoing"
microwave-approval: owner-microwave
microwave-outgoing: :include:/home/majordomo/lists/microwave
owner-microwave-outgoing: owner-microwave
microwave-archive: "|/home/majordomo/wrapper archive -f
/home/majordomo/archives/microwave/microwave -m -a"
owner-microwave-archive: owner-microwave
microwave-request: "/home/majordomo/wrapper request-answer microwave"
owner-microwave-request: owner-microwave
Originally, this was working. Subscribe requests would go to the owners box
and then they could approve them. However, if a mail message is now sent to
microwave-request@wa1mba.org the owner of the list will receive the
following message:
The original message was received at Mon, 27 Sep 1999 14:51:18 -0400
from camby.crocker.com [204.97.12.2]
----- The following addresses had permanent fatal errors -----
"/home/majordomo/wrapper request-answer microwave"
(expanded from: <microwave-request@crocker.com>)
----- Transcript of session follows -----
Message delivered to mailing list owner-microwave
[ Part 2: "Delivery Status" ]
Reporting-MTA: dns; rmc1.crocker.com
Received-From-MTA: DNS; camby.crocker.com
Arrival-Date: Mon, 27 Sep 1999 14:51:18 -0400
Final-Recipient: RFC822; <microwave-request@crocker.com>
X-Actual-Recipient: RFC822; "/home/majordomo/wrapper request-answer
microwave"@rmc1.crocker.com
Action: failed
Status: 5.0.0
Last-Attempt-Date: Mon, 27 Sep 1999 14:51:18 -0400
running config.test reports the following:
------------------------------------------------------------
---------------- Config-test for Majordomo ----------------
------------------------------------------------------------
--------------------- Obvious things: ---------------------
------------------ environment variables ------------------
HOME=/home/majordomo
LOGNAME=root
MAJORDOMO_CF=/home/majordomo/majordomo.cf
PATH=/bin:/usr/bin:/usr/ucb
SHELL=/bin/sh
USER=root
--------------------- euid/egid checks ---------------------
effective user = majordom (uid 17)
effective group = daemon shadow wheel disk adm sys daemon bin root (gid 2
11 10 6 4 3 2 1 0 )
---------------------- uid/gid checks ----------------------
real user = majordom (uid 17)
real group = daemon shadow wheel disk adm sys daemon bin root (gid 2
11 10 6 4 3 2 1 0 )
------------------------------------------------------------
Non obvious things that cause headaches:
------------------------------------------------------------
Good: 'require'd /home/majordomo/majordomo.cf okay.
Good: found ctime.pl okay.
Good: found majordomo_version.pl okay.
Good: found majordomo.pl okay.
Good: found shlock.pl okay.
Good: found config_parse.pl okay.
You're running Majordomo Version 1.94.4.
--==> Majordomo home directory is /home/majordomo.
------------------- Include directories -------------------
/home/majordomo
/usr/lib/perl5/i386-linux/5.00405
/usr/lib/perl5
/usr/lib/perl5/site_perl/i386-linux
/usr/lib/perl5/site_perl
.
--------------------------- Home ---------------------------
Good: changedir to /home/majordomo succeeded.
Good: Created a mock lock file.
---------------------- temp directory ----------------------
Good: Created a temp file in $TMPDIR (/usr/tmp).
---------------------- list directory ----------------------
Good: list directory /home/majordomo/lists has good permissions.
--------------------------- log ---------------------------
Good: logfile /home/majordomo/Log exists and is writeable.
------------------------- Mailers -------------------------
You have defined a mailer for delivery.
Attempting to verify that this is a valid mailer...looks okay.
You have defined a mailer for delivering administrative messages.
Attempting to verify that this is a valid mailer...looks okay.
------------------ Checking majordomo.cf ------------------
Checking to see if there are new variables that should be in
your majordomo.cf file...
Unknown configuration variables in existing majordomo.cf:
$max_loadavg
$uptime
Have you configured where Majordomo is?
$whereami is crocker.com
Good: yup!
----------------------- end of tests -----------------------
Nothing bad found! Majordomo _should_ work correctly.
If it doesn't, check your configuration file
(/home/majordomo/majordomo.cf)
closely, and if it still looks okay, consider asking the majordomo-users
mailing list at "majordomo-users@greatcircle.com" for assistance. Be sure
and fully specify what your problems are, and what type of machine (and
operating system) you are using.
Enjoy!
Any help the list can provide would be appreciated. I can't seem to fix
this problem.
Regards,
Thomas J. Poulin
Operations Manager - Internet Division
Crocker Communications, Inc.
(413) 585-5164 - tpoulin@crocker.com
http://www.crocker.com
|
|
