>> I'm having problems with (surprise, surprise...) the installation of
>> Majordomo 1.94.3 on Linux RED.HAT 2.0.18
>> In the Makefile I specified W_USER as majordom (UID 98) and W_GROUP as
>> majordom (GID 45).
>> The config-test (see copy below) runs fine as a normal user, but I am
>> confused by it saying that the effective (and real) user is daemon (uid 2)
>> and not majordom (UID 98). Why would this be?
>> This is causing problems with the file permissions. I can SUBSCRIBE to
>> 'finanzas' fine, and send messages fine, but trying to UNSUBSCRIBE gives me
>> the message:
>> MAJORDOMO ABORT (mj_majordomo)!!
>> chown(98, 45, "/usr/local/src/majordomo-1.94.3/lists/finanzas.new"):
>> Operation not permitted
>> This file is obviously owned by daemon (see transcript below). What is the
>> function of this file, anyway?
>I suspect that this is another form of the same basic permissions
>problem I ran into with Red Hat Linux 4.1 (kernel 2.0.27). The
>default sendmail.cf makes the DefaultUser mail:mail, not
>daemon:daemon. Where I saw the problem was when sendmail tried to
>read the :include:'ed list of subscribers in the chmod 750 lists
>subdirectory, owned by majordom:majordom. I got a sendmail, not a
>majordomo error. I had added daemon to group majordom, but that
>didn't help. When I added user mail to group majordom, it fixed the
>problem, and I could change the permissions on the directories and
>files back to the more restrictive, non-world-readable settings.
Yeah, I thought of this, and after several installation attempts (all with
permissions problems) I put majordom, mail and daemon all in each other's
groups (and gave it the 'newgrp' command afterwards), unfortunately with no joy.
It seems the problem here is of a different nature:
1.) why does daemon own those files anyway, when I chose majordom as the
W_USER in Makefile?
2.) which user (mail or majordom) is trying to change the ownership of
'finanzas.new' ? Why? Surely this is an illegal operation for any user bar
superuser and the actual owner of the file, or can a member of that file's
group change the ownership if it's in read and write mode for the group?
3.) is there any configuration option I can change to bypass this operation?
I even (as root) changed the ownership manually of the files to majordom,
but then I get this message:
MAJORDOMO ABORT (mj_majordomo)!!
Operation not permitted
I'm stuck, really.
Thanks for the help - any more comments gratefully appreciated.