I am trying to install majordomo-1.93 on a HP 700/15 workstation running
HPUX 9.03 (POSIX-like). We use sendmail and perl 5.001. I know
majordomo is not proven with 5.001 but we don't have version 4.
the error message I get is:
111111111111111111111111111111111111111111111111111111111111111111111
>From MAILER-DAEMON@starfire.ne.uiuc.edu Fri Mar 24 15:58 CST 1995
Received: by starfire.ne.uiuc.edu
(1.37.109.15/16.2) id AA124722338; Fri, 24 Mar 1995 15:58:52 -0600
Date: Fri, 24 Mar 95 15:58:52 CST
From: Mail Delivery Subsystem <MAILER-DAEMON@starfire.ne.uiuc.edu>
Return-Path: <MAILER-DAEMON@starfire.ne.uiuc.edu>
Subject: Returned mail: unknown mailer error 139
To: owner-listserv@starfire.ne.uiuc.edu
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="----- =_aaaaaaaaaa"
Status: RO
------- =_aaaaaaaaaa
Content-Type: text/plain; charset="us-ascii"
Content-Description: Session Transcript
sh: 12474 Memory fault - core dumped
554 "|/usr/local/majordomo-1.93/wrapper majordomo"... unknown mailer error 139
------- =_aaaaaaaaaa
Content-Type: message/rfc822
Content-Description: Returned Content
Received: by starfire.ne.uiuc.edu
(1.37.109.15/16.2) id AA124712332; Fri, 24 Mar 1995 15:58:52 -0600
From: Preston Craig Smith <pres@starfire.ne.uiuc.edu>
Return-Path: <pres@starfire.ne.uiuc.edu>
Subject: now?
To: listserv@starfire.ne.uiuc.edu
Date: Fri, 24 Mar 95 15:58:52 CST
Full-Name: Preston Craig Smith
Mailer: Elm [revision: 70.85]
help
lists
------- =_aaaaaaaaaa--
1111111111111111111111111111111111111111111111111111111111111111111111
The help part of the output is mailed to me and looks alright, but it
only prints part of the lists command output:
2222222222222222222222222222222222222222222222222222222222222222222222
>From pres@starfire.ne.uiuc.edu Fri Mar 24 16:58 EST 1995
Received: by starfire.ne.uiuc.edu
(1.37.109.15/16.2) id AA124772334; Fri, 24 Mar 1995 16:58:54 -0500
Date: Fri, 24 Mar 1995 16:58:54 -0500
Return-Path: <pres@starfire.ne.uiuc.edu>
To: pres@starfire.ne.uiuc.edu
From: listserv@starfire.ne.uiuc.edu
Subject: Majordomo results: now?
Reply-To: listserv@starfire.ne.uiuc.edu
Status: RO
--
>>>> help
This is Brent Chapman's "Majordomo" mailing list manager, version 1.93.
[bulk of helpfile deleted for brevity]
If you have any questions or problems, please contact
"pres".
>>>> lists
listserv serves the following lists:
222222222222222222222222222222222222222222222222222222222222222222222222
It ends right there.
Now for some background on the current setup.
1) We are calling it listserv because everyone on the lists is used to
it since we were running MrTULP until recently. It seems unlikely that
this is the problem anyway.
2) The aliases look like this:
list-errors: pres@starfire.ne.uiuc.edu
listserv : "|/usr/local/majordomo-1.93/wrapper majordomo"
owner-listserv : pres@starfire.ne.uiuc.edu
listserv-owner : pres@starfire.ne.uiuc.edu
test: :include:/usr/local/mail/lists/test
owner-test: pres
test-owner: pres
test-request: "|/usr/local/majordomo-1.93/wrapper request-answer test"
test-approval: pres
3) I think the permissions are alright but for the curious:
drwxrwxr-x 5 listserv listserv 1024 Mar 24 15:58 majordomo-1.93
majordomo-1.93/
total 2748
-rw-rw---- 1 listserv listserv 97 Mar 24 15:13 Log
drwxrwxrwx 2 root users 1024 Mar 24 14:25 Tools
drwxrwxrwx 2 root users 1024 Mar 24 14:25 bin
-rwxr-xr-x 1 root users 2615 Mar 24 15:08 bounce-remind
-rw-r--r-- 1 root users 43737 Mar 24 15:08 config_parse.pl
-rw-rw---- 1 listserv listserv 1217356 Mar 24 15:13 core
-rwxr-xr-x 1 root users 11320 Mar 24 15:08 digest
-rwxr-xr-x 1 root users 42524 Mar 24 15:08 majordomo
-rw-r--r-- 1 root users 3697 Mar 24 15:08 majordomo.cf
-rw-r--r-- 1 root users 14327 Mar 24 15:08 majordomo.pl
-rw-r--r-- 1 root users 141 Mar 24 15:08 majordomo_version.pl
drwxrwxrwx 4 root users 1024 Mar 24 14:25 man
-rwxr-xr-x 1 root users 2153 Mar 24 15:08 new-list
-rwxr-xr-x 1 root users 3024 Mar 24 15:08 request-answer
-rwxr-xr-x 1 root users 12872 Mar 24 15:08 resend
-rw-r--r-- 1 root users 3742 Mar 24 15:08 resend.README
-rw-r--r-- 1 root users 6183 Mar 24 15:08 shlock.pl
-rwxr-xr-x 1 root users 131 Mar 24 15:08 test
-rwsr-xr-x 1 root sys 20480 Mar 24 15:08 wrapper
majordomo-1.93/Tools:
total 16
-rwxr-xr-x 1 root users 7192 Mar 24 15:08 archive2.pl
majordomo-1.93/bin:
total 24
-rwxr-xr-x 1 root users 6219 Mar 24 15:08 approve
-rwxr-xr-x 1 root users 2887 Mar 24 15:08 bounce
-rwxr-xr-x 1 root users 1424 Mar 24 15:08 medit
majordomo-1.93/man:
total 4
drwxrwxrwx 2 root users 1024 Mar 24 14:25 man1
drwxrwxrwx 2 root users 1024 Mar 24 14:25 man8
majordomo-1.93/man/man1:
total 8
-rw-r--r-- 1 root users 3512 Mar 24 15:08 approve.1
majordomo-1.93/man/man8:
total 14
-rw-r--r-- 1 root users 6922 Mar 24 15:08 majordomo.8
4) For completeness, here is the configuration file:
/usr/local/majordomo-1.93/majordomo.cf (there is a symb link in /etc also)
# $whereami -- What machine am I running on?
$whereami = "starfire.ne.uiuc.edu";
# $whoami -- Who do users send requests to me as?
$whoami = "listserv@$whereami";
# $whoami_owner -- Who is the owner of the above, in case of problems?
$whoami_owner = "pres@$whereami";
# $homedir -- Where can I find my extra .pl files, like majordomo.pl?
# the environment variable HOME is set by the wrapper
if ( defined $ENV{"HOME"}) {
$homedir = $ENV{"HOME"};
} else {
$homedir = "/usr/local/majordomo-1.93";
}
# $listdir -- Where are the mailing lists?
$listdir = "/usr/local/mail/lists";
# $digest_work_dir -- the parent directory for digest's queue area
# Each list must have a subdirectory under this directory in order for
# digest to work. E.G. The bblisa list would use:
# /usr/local/mail/digest/bblisa
# as its directory.
$digest_work_dir = '/usr/local/mail/digest';
# $log -- Where do I write my log?
$log = "$homedir/Log";
# $mailer -- What program and args do I use to send mail?
# The variable $to can be interpolated into this command line,
# however the $to variable is provided by the person sending mail,
# and much mischief can be had by playing with this variable.
# Use $to with care.
$mailer = "/usr/lib/sendmail -f\$sender -t";
# Majordomo will look for "get" and "index" files related to $list in
# directory "$filedir/$list$filedir_suffix", so set $filedir and
# $filedir_suffix appropriately. For instance, to look in
# /usr/local/mail/files/$list, use:
# $filedir = "/usr/local/mail/files";
# $filedir_suffix = ""; # empty string
# or to look in $listdir/$list.archive, use:
# $filedir = "$listdir";
# $filedir_suffix = ".archive";
$filedir = "$listdir";
$filedir_suffix = ".archive";
# What command should I use to process an "index" request?
$index_command = "/bin/ls -lR";
# If you want to use FTPMAIL, rather than local access, for file transfer
# and access, define the following:
# $ftpmail_address = "ftpmail@decwrl.dec.com";
# $ftpmail_location = "FTP.$whereami";
# if you want the subject of the request to be included as part of the
# subject of the reply (useful when automatically testing, or submitting
# multiple command sets), set $return_subject to 1.
$return_subject = 1;
# If you are using majordomo at the -request address, set the
# following variable to 1. This affects the welcome message that is
# sent to a new subscriber as well as the help text that is generated.
$majordomo_request = 0;
# Set the umask for the process. Used to set default file status for
# config file.
umask(007);
# the safe locations for archive directories. This should be defined as
# a series of root anchored directory paths as will be used as prefixes
# to the file names specified to the archive2.pl script.
@archive_dirs = ( "/spool/archive/bblisa", "/usr/spool/archive/firewalls" );
# Set this to 1 if you want to use the experimental mechanism for allowing
# / in user names. People with lots of X.400 addresses on their lists or
# HP mail whatever may want to set this. However use it at your own risk.
$analyze_slash_in_address = 0;
#
# these tune the experimental matching that is done for addresses with / in
# them. If you haven't turned on the experimental analyze_slash_in_address
# they are ignored. See the source for full explanation of these variables.
#
# if set to 1 ignore the requirement that addresses have an @ sign in the
# address component after the last /.
$no_x400at=0;
# if set to 1 do not look for "/c=" and "/ad=" or "/am=" in the address.
# X.400 seems to require these components.
$no_true_x400=0;
1;
# $Header: /sources/cvsrepos/majordomo/sample.cf,v 1.4.2.1.2.2 1995/01/07 17:35:03 rouilj Exp $
Any help on this would be great. Currently I have 5 mailing lists that
are at a stand still..... eeek.
Preston Smith
psmith@uiuc.edu
|
|
