[Mailman-Users] Public Archives 403 Forbidden after Upgrade - More Info
carbonnb at sympatico.ca
Mon Sep 19 17:23:02 CEST 2005
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. on RedHat 7.3 (thats what the host supplies)
Mailamn was configured with the following commande:
./configure --prefix=/var/mailman --with-
python=/usr/local/bin/python --with-cgi-gid=apache --wit
My Apache directives are:
Alias /pipermail/ /var/mailman/archives/public/
Options +FollowSymLinks +Indexes
The error in Apache's access_log is:
xx.xx.xx.x - - [19/Sep/2005:10:12:30 -0500] "GET /pipermail/accessd
HTTP/1.1" 403 304 "-" "BROWSER ID STRING"
There is nothing that I can see in the MM error logs or in the
bin/check_perms shows no errors
the permissions on the archives directories are:
drwxrws--- 60 root mailman 4096 Sep 19 09:58 private
drwxrwsr-x 2 root mailman 4096 Sep 19 09:59 public
and all the symlinks in public point to the right spot in the private
archives. I can follow the symlinks from the command prompt as root
or another user. If I create a symlink in the public directory to
another file or directory in the file system, I can access those
files/directories from my browser. I just can't get to the private
If I treat the archive as a private archive by going to:
http://example.com/mailman/private/listname/ I can log in and access
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 not.
Bryan Carbonnell - carbonnb at sympatico.ca
Give a man a fire, he will be warm for the evening. Set a man on
fire, he will be warm for the rest of his life.
More information about the Mailman-Users