Thanks for this, Dan. I'll try it again today. I have a couple of questions
about what you wrote. Fyi, I've worked with solaris for a couple of years,
but infrequently, so my level of expertise is low.
1a. What is Tmajordom/Tmajordomo? I don't see this in the documentation. If
it's not there, do you mind explaining to this majordomo novice why it's
needed?
7. At first I was indeed having trouble with make install, as you indicated,
but got past it.
10. My config-test eventually came back with 0 errors, but I couldn't send
to any lists. After I got the log working (also didn't install correctly,
despite no error saying so), I saw that I had the wrong ownerships and
permissions for the list files. Once I changed those, I could send to my
lists.
What I can't do is any list administration such as subscribing and
unsubscribing people or who or which commands. That's what I was asking
about yesterday, but I know my message was rather long. Here's a log entry
for list administration commands:
Jun 05 13:38:26 lakenet.org majordomo[28550] {<listowner@org.org>} approve
PASSWO
RD unsubscribe flls-l user@org.org
Jun 05 13:38:26 lakenet.org majordomo[28550] {<listowner@org.org>} ABORT
Can't op
en /opt/majordomo-1.94.5/lists/flls-l.new: Permission denied
I was asking about the flls-l.new file that majordomo automatically created,
why it's there, what permissions it needs, or how to get rid of it.
Catharine
-----Original Message-----
From: majordomo-users-owner@greatcircle.com
[mailto:majordomo-users-owner@greatcircle.com]On Behalf Of Daniel Liston
Sent: Friday, June 06, 2003 1:35 AM
To: croberts@lakenet.org
Cc: majordomo-users@greatcircle.com
Subject: Re: listname.new and ownership of files
I posted a recipe for a successful install a couple years back. Let me see.
My current configuration has a link to perl in /bin from /usr/bin, not that
it should matter, and cc is linked to gcc in /usr/bin.
These are my install steps.
1. create a majordom user and group in /etc/passwd and /etc/group.
note1: "majordomo" if no 8 character limitation in your OS
1a. add "Tmajordom" to /etc/sendmail.cf # or Tmajordomo
2. make note of the uid:gid of this user, and the $HOME directory
3. locate your perl and gcc tools, you need this in the next step
4. edit Makefile
4a. PERL = /usr/local/bin/perl
4b. CC = /usr/local/bin/gcc
4c. W_HOME = /opt/majordomo # <$HOME from above in step 2>
4d. MAN = $(W_HOME)/man # /usr/man or /usr/local/man
4e. W_USER = 400 # uid from above in step 2
4f. W_GROUP = 400 # gid from above in step 2
note4ef: These must match the 3rd and 4th column of /etc/passwd
4g. The following defaults are fine;
FILE_MODE = 644
EXEC_MODE = 755
HOME_MODE = 751
4h. Your OS is POSIX so these are fine too;
WRAPPER_OWNER = root
WRAPPER_GROUP = $(W_GROUP)
WRAPPER_MODE = 4755
POSIX = -DPOSIX_UID=$(W_USER) -DPOSIX_GID=$(W_GROUP)
TMPDIR = /var/tmp
5. copy sample.cf to majordomo.cf
5a. edit majordomo.cf. I only list lines needing changes
$whereami = "example.com"; # change to your domain
$homedir = "/opt/majordomo"; # same as above in 2 and 4c.
$digest_work_dir = "$homedir/digests"; # note plural
$sendmail_command # uncomment the line appropriate to your OS
$TMPDIR = $ENV{'TMPDIR'} || "$homedir/tmp";
note5: Make sure you are the root user in bash or sh shell
6. make wrapper
7. make install # is this where your process dies now?
8. make install-wrapper
9. edit /etc/aliases to add/modify;
majordomo: "|/opt/majordomo/wrapper majordomo"
owner-majordomo: you,
majordomo-owner: owner-majordomo
10. If you got past steps 6, 7, and 8 (#perl problem#)
cd <directory in step 2, 4.c and 5.a> then ./wrapper config-test
Once this comes back successful, it is majordomo admin as usual. :)
Sendmail will squawk about any directory in the path to a list that
is world or group writable. They can be executable/searchable but not
writable. Sendmail will also complain about the group writable permission
on your list file. Notice the ownerships and permission on the example
provided in the sendmail FAQ.
http://www.sendmail.org/faq/section3.html#3.32
Have you tried using my newlist.pl script?
Additional reading for your listowners, Doc/list-owner-info.
Dan Liston
Catharine Robertson wrote:
> I was able to run a config-test that returned 0 errors after mucking
around
> with some permissions. So now I can send to my lists (from migrated data),
> but no listowners are able to do any adding or deleting. I have read and
> reread the FAQ, the INSTALL doc, and the README doc, but I'm still getting
> error messages about "not owner."
>
> Can some kind soul offer another pair of eyes to spot what I'm obviously
> missing?
>
> Here's an example of a list for which it's possible to send messages, but
> the owner cannot make any changes:
>
> -rw-rw-r-- 1 majordom daemon 826 Jun 5 13:09 flls-l
> drw-rw-r-- 2 majordom daemon 1536 Jun 4 14:17 flls-l.archive
> -rw-rw-r-- 1 majordom majordom 12107 Jun 4 14:17 flls-l.config
> -rw-rw-r-- 1 majordom daemon 397 Jun 4 14:17 flls-l.info
> -rw-rw-r-- 1 majordom daemon 6 Jun 4 14:17 flls-l.passwd
>
> (I got errors sending to the list until I changed the ownership of
> flls-l.config to majordom:daemon).
>
> And here's a log entry from when he tried to make changes to the list.
>
> Jun 05 13:38:26 lakenet.org majordomo[28550] {<listowner@org.org>} approve
> PASSWO
> RD unsubscribe flls-l user@org.org
> Jun 05 13:38:26 lakenet.org majordomo[28550] {<listowner@org.org>} ABORT
> Can't op
> en /opt/majordomo-1.94.5/lists/flls-l.new: Permission denied
>
> Why is majordomo creating a file called flls-l.new? Should it be? If yes,
> what should its ownership and permissions be? I've tried all permutations
of
> majordom:majordom, majordom:daemon, mailnull:smadmin, 660, and 664. If no,
> how can I get rid of it? I've also tried deleting the file outright, but
it
> gets created again, with the ownership of mailnull:smadmin. But then I get
> errors about it running with the wrong uid and gid.
>
> Additionally, all the directories in the path leading to flls-l.new,
> /opt/majordomo-1.94.5/lists, have permissions of 750 or 755, as specified
in
> the FAQ.
>
> Please help!
>
> Catharine
>
References:
|
|
