On Fri, 23 Feb 2001, Robin Sanders wrote:
>
> -
>
> I wrote:
>
> > But everytime someone attempts to "uns_bscribe" to a list, I
> > get the following error message bounced back to my account
> > (as the majordomo caretaker):
> >
> > >
> > > MAJORDOMO ABORT (mj_majordomo)!!
> > >
> > > chown(851, 12, "/usr/local/majordomo-1.94.5/lists/mat164.new"): Operation not permitted
>
> and ishwar@pali.cps.cmich.edu responded:
>
> > What are the permissiosn on this path?
> >
> > > By the way, majordomo has UID 851 and the group "mail" has GID 12.
> >
> > Isn't majordomo user has to have its own group ?
>
> The user is majordomo and the GID is 12 for the path. Both the
> user and group have rwx on both the majordomo-1.94.5 and lists
> directories.
>
> In RedHat Unix every user (including majordomo) does have its
> own singleton group---the group "majordomo" has GID 852, but you
> can put users in multiple groups. If I make the "group" of
> the lists directory 852, then I get a different set of MAJORDOMO ABORT
This is the problem..
> messages whenever anyone tries to do anything with my mailing lists.
>
> I'm now beginning to wonder if this is some kind of a weird
> problem with my system's chown. But I can't figure out which
> "user" (mail or majordomo) is attempting to do the chown command
> or why a chown command is being done.
>
> Additonal information: The file mat164.new is NOT present in the
> lists directory before someone tries to unsubscribe; once it's
> created an "ls -l" shows that the file is owned by "mail (UID 8)"
> with group set to "mail (GID 12)." The permissions on the file
> are rwxrwxr-- and "majordomo" is part of the group "mail".
The file should be owned by majordomo
In worst case scenario you can get the original majordomo instead
of using the rpm (never had success with it), also it is possible to
delete member manually (may be they can send unsubscribe requests to
list)..
|
|
