[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [cobalt-users] alias :include: SOLVED



Ahoy Davis and friends.

Solved the include group write problem, at least on my RaQ2.  Grab a beer
and read along.  Seems that not only can the directory containing the
include file not be group writeable - neither can any of its parent
directories!  If you don't want to read the details you can skip to
"********************".

Note: In all cases the directory containing the file mylist was 755 and
mylist was oned by admin:daemon and was 644.

First I created an include file in /home/majordomo/lists
(there is a symbolic link in /usr/local of majordomo -> /home/majordomo/).

Then I created a record in aliases.majordomo of:
mylist:    :include:/home/majordomo/lists/mylist
The mail was forwarded to both local and external recipients.
mylist:    :include:/usr/local/majordomo/lists/mylist also worked.

It also worked in /home ( include file of /home/mylist).

I also tried putting mylist in /root, but I got:
550 :include:/root/mylist... Cannot open /root/mylist: Permission denied
554 <mylist@mydomain>... aliasing/forwarding loop broken

********************
I also tried putting mylist in /home/sites/siteX/lists, but I got:
550 :include:/home/sites/siteX/lists/mylist...
Cannot open /home/sites/siteX/lists/mylist: Group writable directory
554 <mylist@mydomain>... aliasing/forwarding loop broken

Odd.  /home/sites/siteX/lists is 755 (no group write access).  It wasn't
intuitive to me why I could have an include in /home/majordomo/lists, and
/home, but not in /home/sites/siteX/lists so I did some more testing.  I
decided to change the permissions on /home/sites/siteX from drwxrwsr-x to
drwxr-xr-x by chmod g-s, chmod 755.  Wa-la!  An include in
/home/sites/siteX/lists now works!

But, what will the change in permissions affect?  Is there any harm in this
solution?  I'm asking b/c I'm not a Linux guru and though it may be obvious
to you it isn't to me.  BTW, your beer should be finished by now.

Steven {steven@xxxxxxxxxxxx}