In message <9411102203.AA08182@pixelnet.pixel.com.mx>, "Giraldo Hierro" writes:
> As specified in the installation guide, wrapper's uid is set to daemon
>and it's gid is majordom. Also, I put daemon inside the majordom group in
>/etc/groups, and made sure all files are both uid read-writable and gid
>read-writable. I made a lists directory where I install lists, and made
>that u+rw and g+rw.
> I still have problems, though. If any .config file inside the lists
>directory isn't read-writable by "others" (o+rw), majordomo will balk
>on such simple commands as "lists". And, when creating new lists (by
>creating a blank file with the listname), Majordomo creates a <list>.config
>file with daemon as the uid and gid, OR with a local user's uid when the
>mail request came from a local user.
You missed a critical section of the FAQ.
If you are on a non-POSIX system, the wrapper must be both suid and
sgid (mode 6755) to whatever you defined your majordomo user and group
to be. It must not be setuid root!
In a POSIX system the wrapper must be setuid root, and double-check
that W_UID and W_GID are of the majordomo user and group. Don't set
W_UID to be 0!
It sounds like from both your symptoms and your description that
you don't have the wrapper both suid and sgid.
This is by far the most confusing thing about Majordomo -- getting
the wrapper permissions right, and getting the directory permissions
right. I'm going to re-organize the FAQ slightly to merge all the
permission-related problems under one question, with explicit instructions
on how things must be set. Other questions which are a symptom of
incorrect permissions will simply refer to the "how do i set permissions
on all the Majordomo files and directories?" question.