Thanks for all your help. There is a file I found in the MajorCool
Distribution called cpset. Here is an exerpt from the file:
USAGE="usage: Cpset [-o] from-file to-file mode owner group"
Seems that there is a specific relationship between MajorCool and Majordomo
that needs to be set during the install and majordomo should be working
first properly. As I'm learning more about Majordomo though, I think I'll
forgo the web interface. MajorCool has weak authentication.
I guess I'll be setting up archiving and digesting next. Wish me luck
Thanks for all your help.
[mailto:majordomo-users-owner@GreatCircle.COM]On Behalf Of Daniel Liston
Sent: Wednesday, October 17, 2001 11:33 AM
Subject: Re: aliasing/forwarding loop broken
775 on /majordomo is still going to cause complaints from sendmail unless
one of the "dontblamesendmail" options is enabled.
UID 1000 GID 33 does not really say anything, unless that is your sendmail
or majordomo ID.
I know VERY LITTLE about majorcool. Mostly, only what I have picked up
from reading the majordomo-users list. I don't use it or any other form
of http access to my servers. Having set it up several years ago, I recall
it being a bit unintuitive and still required additional scripts to be
written before it was fully functional. Plus all the ownership/permission
problems to solve between apache, majordomo, and sendmail was a bad enough
headache on a server that I have full root control of. Trying to do all
that in a hosted environment is even worse.
The answer I provided with the chmod command will solve the sendmail error
messages related to majordomo. If you want/need majorcool, someone else
will need to provide the assistance. I just do not have the knowledge.
"Michael R. Welch" wrote:
> I seem to have cleared up the errors, at least with majordomo. My host
> provider origionally installed Majordomo files and folders with 777
> permissions. The only thing I couldn't get to work was sending mail to the
> list. This includes MajorCool. Reducing the permissions on the permissions
> to 755 (what you suggested) makes it so the majorcool interface doesnt
> So I changed /majordomo permissions to 775 and at least the interface
> and majordomo still is working.
> This is the error I get when I try to see what lists my 1 loney lest
> is subscribed to:
> : ABORT
> shlock: '/majordomo' is not writable by UID 1000 GID 33
> This suggests a permissions error like MajorCool is not part of the
> group to me with my limited knowlege of permissions.
> As I recall the only time MajorCool fully worked is if the entire
> tree had permissions set to 777, which is the way I found this mess.
> any ideas?
> -----Original Message-----
> From: majordomo-users-owner@GreatCircle.COM
> [mailto:majordomo-users-owner@GreatCircle.COM]On Behalf Of Daniel Liston
> Sent: Tuesday, October 16, 2001 10:49 PM
> To: Michael R. Welch
> Cc: Majordomo-users
> Subject: Re: aliasing/forwarding loop broken
> This means a directory in the tree to your list has group writable
> permission enabled. As root, do this;
> cd /
> chmod -R go-w majordomo
> Dan Liston
> "Michael R. Welch" wrote:
> > What does this indicate?
> > ----- Transcript of session follows -----
> > 550 :include:/majordomo/lists/free-pctech-news
> > .. Cannot open /majordomo/lists/free-pctech-news: World writable
> > Message delivered to mailing list
> > 554 <firstname.lastname@example.org>... aliasing/forwarding
> > broken