[Mailman-Users] permission denied on archive

[Richard Barrett]

On 26 Nov 2003, at 17:25, Brian Craft wrote:

>
>
> On Wed, Nov 26, 2003 at 08:21:53AM +0100, Sasa Stupar wrote:
>> Brian Craft wrote:
>>
>>> I just went through the INSTALL doc and set up the /pipermail/ alias.
>>> The archive links now give me a permission denied error.
>>>
>>> The permissions on the directories are as shown:
>>>
>>> drwxrws---    6 root     list         4096 Nov 25 18:05 private
>>> drwxrwsr-x    2 root     list         4096 Nov 25 18:05 public
>>>

These are not correct the permissions for the $prefix/archives/private 
directory which should be:

     drwxrws--x    6 root     list         4096 Nov 25 18:05 private

Without other having execute permission on $prefix/archives/private, 
symlinks in $prefix/archives/public, accessed via the /pipermail/ URI, 
cannot be followed by the Apache server. This is the cause of the 
permissions failure you are seeing. Apapche also must have 
+FollowSymLinks on the Options directive applicable to 
$prefix/archives/public.

>>> Is this correct? If I add "other" read & execute to the "private"
>>> directory, then the archive links works. But I doubt that's the
>>> right solution.
>>>

You do not need to open up read permission to other on 
$prefix/archives/private. This will allow anybody with access to the 
command line of your system to read private archives, which may or may 
not be acceptable to you.

>>> I don't really understand this private/public directory business and 
>>> the
>>> symbolic links between them. Can someone explain what the goal is?
>>>

With the private/public directory setup, list archives can be changed 
from private to public and vice versa by simply adding and deleting 
symlinks in the $prefix/archives/public directory to subdirectories in 
the $prefix/archives/private directory. This is what happens when you 
change the public/private archiving option through the web admin GUI.

>>> b.c.
>> run bin/check_perms -f to see if you have correct permissions.
>
> It reports no problems,

Maybe it should. I'll take a look at the check_perms code. Another 
question is how the $prefix/archives/private directory got created with 
the wrong permissions during the installation. How did you install MM 
and what version are you running on what OS.

> but I still get "permission denied" on the archive
> from apache.
>
> b.c.
>
-----------------------------------------------------------------------
Richard Barrett                               http://www.openinfo.co.uk