On Sun, 23 Apr 2006 17:04:27 -0700, Mark Sapiro wrote
> Noah wrote:
> >
> >I hear what you are saying but not completely understanding your analysis.
> >The point of the permissions and ownership changes is so the web server has
> >access to the private directory. And then to o-x the private dire
Noah wrote:
>
>I hear what you are saying but not completely understanding your analysis.
>The point of the permissions and ownership changes is so the web server has
>access to the private directory. And then to o-x the private directory keeps
>local users from accessing the private directories
On Sun, 23 Apr 2006 11:49:12 -0700, Mark Sapiro wrote
> Noah wrote:
> >
> >Well the sym links appear to work fine from an apache/browser perspective. I
> >dont think there has been any problems yet.
> >
> >archiving appears to be working properly for both public and private
> >archives.
>
> The
Noah wrote:
>
>Well the sym links appear to work fine from an apache/browser perspective. I
>dont think there has been any problems yet.
>
>archiving appears to be working properly for both public and private archives.
The issue is not whether one or the other will work or not from the
Apache p
>
> >but what I did do was remove all other permissions and put the ownership of
> >the private directory to www to solve the problem. check_perms works well
> >now.
> >
> ># ls -l
> >total 6
> >drwxrws--- 103 www mailman 2560 Apr 21 21:49 private
> >drwxrwsr-x2 mailman mailman 153
Noah wrote off list:
>after a 'chmod o+x private/' the public and private mailman archives are
>visible.
>
>but now when I run the bin/check_perms -f I see the following warning:
>
># ./check_perms -f
>Warning: Private archive directory is other-executable (o+x).
>This could allow other u
mailman-2.1.7
apache 2.2.0
FreeBSD-4.11
Thanks again for all your help.
I never found anything in the intsallation manual as the check_perms message
suggests.
but what I did do was remove all other permissions and put the ownership of
the private directory to www to solve the problem. check_pe
mailman-2.1.7
apache 2.2.0
FreeBSD-4.11
Okay I just upgrade from apache 1.3.x to apache 2.2.0 and arriving at a
permissions problem when viewing pipermail mailman directories.
I've asked already but Maybe somebody else on the list can help. I apologize
for the duality but I cant figure it out
On Fri, 21 Apr 2006 19:37:43 -0700, Mark Sapiro wrote
> Noah wrote:
> >
> >now I changed this:
> >
> >lrwxr-xr-x 1 root mailman 54 Apr 21 19:00
> >/usr/local/mailman/archives/public/list ->
> >/usr/local/mailman/archives/private/list
>
> And do you still have the same error in the apache error_
Noah wrote:
>
>now I changed this:
>
>lrwxr-xr-x 1 root mailman 54 Apr 21 19:00
>/usr/local/mailman/archives/public/list ->
>/usr/local/mailman/archives/private/list
And do you still have the same error in the apache error_log?
If so, this would seem to be an Apache configuration issue rather
On Fri, 21 Apr 2006 18:48:38 -0700, Mark Sapiro wrote
> Noah wrote:
> >
> >lets look at the dirs involved:
> >
> >drwxrws--- 101 mailman mailman 2560 Apr 13 17:49
> >/usr/local/mailman/archives/private
> ># ls -ld /usr/local/mailman/archives/private/list
> >drwxrwsr-x 50 www www 4096 Apr 17 2
Noah wrote:
>
>lets look at the dirs involved:
>
>drwxrws--- 101 mailman mailman 2560 Apr 13 17:49
>/usr/local/mailman/archives/private
># ls -ld /usr/local/mailman/archives/private/list
>drwxrwsr-x 50 www www 4096 Apr 17 21:40
>/usr/local/mailman/archives/private/list
This should be owned b
Noah wrote:
>
>Symbolic link not allowed or link target not accessible:
>/usr/home/mailman/archives/public/news, referer:
>http://domain.garbled.com/mailman/listinfo/news
>
In the OP you said you had for the appropriate virtual host
Options +FollowSymlinks
So
On Fri, 21 Apr 2006 11:51:17 -0700, Mark Sapiro wrote
> Noah wrote:
> >
> >Forbidden
> >
> >You don't have permission to access /pipermail/dir_garbled/ on this server.
> >
> >Additionally, a 403 Forbidden error was encountered while trying to use an
> >ErrorDocument to handle the request.
> >Apache
Noah wrote:
>
>Forbidden
>
>You don't have permission to access /pipermail/dir_garbled/ on this server.
>
>Additionally, a 403 Forbidden error was encountered while trying to use an
>ErrorDocument to handle the request.
>Apache/2.2.0 mod_ssl/2.2.0 OpenSSL/0.9.8a DAV/2 PHP/4.4.2 Server at
>garbled.d
On 4/20/06, Noah <[EMAIL PROTECTED]> wrote:
> Additionally, a 403 Forbidden error was encountered while trying to use an
> ErrorDocument to handle the request.
It sounds like you have more problems with your Apache install thank
you think. Is it running under the same user/group as before?
Did you
On Thu, 20 Apr 2006 23:59:04 +0300, Odhiambo Washington wrote
> * On 20/04/06 07:25 -0800, Noah wrote:
> |
> | mailman-2.1.7
> | apache 2.2.0
> |
> | Okay I just upgrade from apache 1.3.x to apache 2.2.0 and arriving
> at a | permissions problem when viewing pipermail mailman
> directories: | |
* On 20/04/06 07:25 -0800, Noah wrote:
|
| mailman-2.1.7
| apache 2.2.0
|
| Okay I just upgrade from apache 1.3.x to apache 2.2.0 and arriving at a
| permissions problem when viewing pipermail mailman directories:
|
|
| ---s nip ---
|
| You don't have permission to access /pipermail/garbled-na
mailman-2.1.7
apache 2.2.0
Okay I just upgrade from apache 1.3.x to apache 2.2.0 and arriving at a
permissions problem when viewing pipermail mailman directories:
---s nip ---
You don't have permission to access /pipermail/garbled-name/ on this server.
--- snip ---
Here is what I've done so
On Apr 9, 2006, at 12:01 PM, Noah wrote:
> On Sun, 9 Apr 2006 11:26:23 -0500, Larry Rosenman wrote
>> On Apr 9, 2006, at 10:56 AM, Noah wrote:
>>
>>>
>>>
>>> Hi folks,
>>>
>>> Okay I just upgraded to the latest apache 2.2.0 and using the same
>>> configuration files as I had for apache1.3 but I a
On Sun, 9 Apr 2006 11:26:23 -0500, Larry Rosenman wrote
> On Apr 9, 2006, at 10:56 AM, Noah wrote:
>
> >
> >
> > Hi folks,
> >
> > Okay I just upgraded to the latest apache 2.2.0 and using the same
> > configuration files as I had for apache1.3 but I am finding there are
> > permission errors when
On Apr 9, 2006, at 10:56 AM, Noah wrote:
>
>
> Hi folks,
>
> Okay I just upgraded to the latest apache 2.2.0 and using the same
> configuration files as I had for apache1.3 but I am finding there are
> permission errors when going to my mailman listinfo directories.
>
> any clues what I need to c
Hi folks,
Okay I just upgraded to the latest apache 2.2.0 and using the same
configuration files as I had for apache1.3 but I am finding there are
permission errors when going to my mailman listinfo directories.
any clues what I need to check here?
actual error message
Forbidden
Yo
I have installed Mailman with the Redhat rpm, and configured everything, but
I get a Forbidden: You don't have permission to access error when I go to
mysite/mailman/
I have tried various settings for users and group ownership of the cgi
files, but can't seem to get it to work. Any suggestions?
24 matches
Mail list logo
