On Wed, 24 Feb 1999, Kevin Hancock wrote:
> My system is Redhat 5.1, Perl 5.004 and
> majordomo-1.94.4.
>
> I have installed majordomo by following the
> INSTALL
>
> 1) created a group majordomo.daemon
> "majordomo.daemon:x:600:"
> created a user majordomo.daemon
> "majordomo.daemon:*:503:600:::"
I take it you have user majordomo, UID 503, and group daemon, GID 600 ?
Looks funny to me, as group daemon usually has a single-digit GID on all
my systems, but this isn't a problem, per se.
From my /etc/passwd:
majordom:x:507:507:Majordom:/home/majordom:/bin/bash
And /etc/group:
daemon::2:root,bin,daemon,majordom
RedHat likes to create a new group for every user, so I just added this
user to the daemon group as well.
>
> 4) edited the majordomo.cf file
> $whereami = "scooby.arcom.com.au";
> $whoami = "majordomo\@$whereami";
> $whoami_owner = "root\@$whereami";
> $homedir = "/usr/local/majordomo";
> $listdir = "$homedir/lists";
>
Only problem I see here is having majordomo owned by root. On the
system I maintain, I point it at my personal account.
> 8) edited /etc/aliases
>
> majordomo:"|/usr/local/majordomo-1.94.4/wrapper majordomo"
> owner-majordomo: root, (also tried majordomo.daemon)
> majordomo-owner: root (also tried majordomo.daemon)
>
I believe wrapper should be installed in the majordomo-home directory.
Although, as I look closely at my own config, I see the same thing. I
specified $homedir as /usr/local/majordomo/, and what I've actually got is
/usr/local/majordomo-1.94.4/ I wonder if `make install` renames the
directory and plugs the version number in there? In any case, the alias
should have the full path to the real location of wrapper. `locate
wrapper` will give you the answer.
Also, majordomo-owner and owner-majordomo should be you, not root.
> 9) ./wrapper config-test ran OK (said "Should be
> OK")
>
> 10) now here is the problem.
> % touch /path/to/majordomo/lists/test
> % echo 'lists' | mail majordomo
>
> Sends mail to root
>
> From: root<root@scooby.arcom.com.au>
> To: root@scooby.arcom.com.au
> Subject: MAJORDOMO ABORT (mj_majordomo)
> --
> MAJORDOMO ABORT (mj_majordomo)!!
> root@scooby.arcom.com.au punting to avoid mail
> loop.
If you were root when you issued that command, that would be the
expected behaviour.
> I then set up the test list as per NEWLIST
>
> and added into my /etc/aliases
>
> test: "|/usr/test/majordomo-1.94.3/wrapper resend -l test test-list"
> test-list: :include:/usr/test/majordomo-1.94.3/lists/test
> owner-test: majordomo.daemon, (also tried root)
> test-owner: majordomo.daemon (also tried root)
> test-request: "|/usr/test/majordomo-1.94.3/wrapper majordomo -l
> test"
Again, where is wrapper really installed? Also, make the list-owner and
owner-list a real person, not the superuser.
majordomo.daemon is the UID.GID that the majordomo process runs as.
majordomo-owner is the real person who installs and maintains majordomo
at that site. The person who sets up new lists, etc. (you!)
<listname>-owner is the person who configures and maintains a particular
list. Quite often, this person is a client account, and not
necessarily one who has any real access to the machine. THat's
one of the beauties of majordomo - the lists themselves may be
configured, managed and maintained completely through e-mail
alone.
> 7) Now issue a 'config <listname>
> <listname>.admin' command to
> Majordomo.
>
> What exactly does that mean ? how do I issue a
> command to majordomo?
All commands to majordomo are in the body of an email sent to
<majordomo@hostname.dom>. From a shell prompt, you could:
`echo "config test test.admin" | mail majordomo` to accomplish
this.
--
Rick Green
Please note my new address: <rtg@mich.com>
--------------------------------------------------------------------
Microsoft has just announced it is renaming Windows NT version 5 to
"Windows 2000."
Is that the ultimate millennium bug or what?
References:
|
|
