[Mailman-Users] (Beer) problem accessing the archive (403)

[Mark Sapiro]

Scriber, Brian wrote:
>
>This is the error message I'm receiving:
>
>Forbidden
>You don't have permission to access /pipermail/is_pmc_interest/ on this
>server.
>Additionally, a 403 Forbidden error was encountered while trying to use
>an ErrorDocument to handle the request.
>  _____  
>Apache/2.0.47 (Linux/SuSE) Server at jedi.icat.com Port 80
>
>
>
>I have run the check_perms script and I have no errors.
>I have the following configuration in my default-server.conf apache
>file:
>
>#########################
>####   MAILMAN
>#########################
>
>ScriptAlias /mailman/ "/usr/local/mailman/cgi-bin/"
>
><Directory "/usr/local/mailman/cgi-bin/">
>	AllowOverride None
>	Options ExecCGI
>	Order allow,deny
>	Allow from all
></Directory>
>
>Alias /pipermail/ "/usr/local/mailman/archives/public/"
>
><Directory "/usr/local/mailman/archives/public/">
>	AddDefaultCharset Off
>	Options Indexes MultiViews FollowSymLinks
>	AllowOverride None
>	Order allow,deny
>	Allow from all
></Directory>
>
>RedirectMatch /mailman[/]*$ http://jedi.icat.com/mailman/listinfo


This is not the cause of your problem, but the above should be

RedirectMatch ^/mailman[/]*$ http://jedi.icat.com/mailman/listinfo

or you'll have difficulty reaching the admin pages for the 'mailman'
list.


>#########################
>#####   End Mailman
>#########################
>
>
>
>Has anyone else run across this problem and solved it?


Lots of people have solved it, but the solution depends on the cause
which we don't yet know in your case.

Are you perhaps running SELinux or some other 'enhanced' access
controls that might be blocking your access?


>Getting to the archives is my primary objective, but I'm curious about
>the third line in the error page as well.  Ideas?


You can probably access the archives via
<http://jedi.icat.com/mailman/private/is_pmc_interest/> except that
way requires authorization as a list owner or member, and when I try
it, I find no DNS entry for jedi.icat.com.

As far as the 403 on attempting to access an error document is
concerned, check your Apache error_log and see what it says. You might
get additional info about the initial error too.


>If you're anwhere near the Denver area I'd be happy to thank you for
>your help (beer).


Sorry, it's a bit far for me to go :-)

-- 
Mark Sapiro <msapiro at value.net>       The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan