[Mailman-Users] Public Archives 403 Forbidden after Upgrade to 2.1.6

[Bryan Carbonnell]

I have recently upgraded to MM 2.1.6 with the HTDig integration 
patches.

I have noticed that since this upgrade that my public archives are 
inaccessible, I get a 403 Forbidden Error.

I am running MM2.1..6 built from the tarball, Apache 1.3.27 and 
Python 2.3.4.

Mailamn was configured with the following commande:
./configure  --prefix=/var/mailman --with-
python=/usr/local/bin/python --with-cgi-gid=apache --wit
h-mail-gid=mail

My Apache directives are:

#
# Configure Mailman's CGI scripts
# From Mailman Users Archive
#

ScriptAlias /mailman/ /var/mailman/cgi-bin/
<Directory /var/mailman/cgi-bin>
  Options -Indexes -FollowSymLinks -Includes ExecCgi
  AllowOverride None
  Order deny,allow
  Allow from all
</Directory>

#
# Configure the public archives
#
Alias /pipermail/ /var/mailman/archives/public/
<Directory /var/mailman/archives/public/>
  Options FollowSymlinks
  AllowOverride None
  Order deny,allow
  Allow from all
</Directory>

The error in my Apache log is:
67.68.49.67 - - [15/Sep/2005:07:42:18 -0500] "GET /pipermail/accessd/ 
HTTP/1.1" 403 305 "-" "Mozilla/5.0 (Windows; U; Windows NT 5.1; en-
US; rv:1.7.10) Gecko/20050716 (No IDN) Firefox/1.0.6"

There is nothing that I can see in the MM error logs.

bin/check_perms shows no errors

One thing is that if I treat the archive as a private archive by 
going to:
http://example.com/mailman/private/listname/
I can log in and access the archives.

I have tried making the archive private and then making it public 
again and it doesn't work.

Does anyone have any ideas of what I can check next. I'm at a total 
loss as to what could be wrong.

Thanks for reading this far.

-- 
Bryan Carbonnell - carbonnb at sympatico.ca
Be who you are and say what you feel because those who mind don't 
matter and those who matter don't mind - Dr.Seuss