Thanks. That and fixing a missing symlink did the trick.
At 7:24 AM -0700 7/5/08, Mark Sapiro wrote:
chmod g+s will do it, but just to make sure everything is right, do it
this way:
chmod 2770 /usr/local/mailman/archives/private
chown nobody:mailman /usr/local/mailman/archives/private
chmod
Bill Christensen wrote:
>At 6:59 PM -0700 7/4/08, Mark Sapiro wrote:
>>
>>What does Apache say when you try to access a public archive? What's in
>>Apache's error log?
>
>Symbolic link not allowed.
This says you need
Options +FollowSymLinks
in a
or superordinate block.
>>What are the owne
At 6:59 PM -0700 7/4/08, Mark Sapiro wrote:
Bill Christensen wrote:
I just moved my Mailman/Apache/Postfix server to a new hard drive,
and in the process managed to make the public archives inaccessible.
Private archives work fine, as does everything else as far as I can
tell.
I suspect that t
Bill Christensen wrote:
>
>I just moved my Mailman/Apache/Postfix server to a new hard drive,
>and in the process managed to make the public archives inaccessible.
>Private archives work fine, as does everything else as far as I can
>tell.
>
>I suspect that the problem has to do with my renaming
Hi folks,
I just moved my Mailman/Apache/Postfix server to a new hard drive,
and in the process managed to make the public archives inaccessible.
Private archives work fine, as does everything else as far as I can
tell.
I suspect that the problem has to do with my renaming the root hard
dri
