[Mailman-Users] Problems with Mailman under 'secure' Linux kernels

[Barry A. Warsaw]

>>>>> "MB" == Mike Burton <mburton at jo.birdsense.com> writes:

    MB> Thank you, Richard.  This sounds like a reasonable answer to
    MB> what is happening.  I'm not sure that I want to reload Lunix
    MB> to accomplish setting up Mailman.  I certainly hope there is a
    MB> workaround that someone can share.  I also didn't mention that
    MB> this was only through the web interface.  I can use the mail
    MB> interface to subscribe without incident.  Oh well, guess I'll
    MB> just have to sit back and see if there is an answer for this
    MB> problem that comes forth.  Otherwise I guess I'm just not
    MB> going to be able to consider Mailman on my system.  Bummer...

Has README.LINUX not helped?  I'm attaching a few files from Mailman
2.1 just in case they have more useful or up-to-date information.
The script itself is probably too MM2.1-centric, but it might be
useful so I'm including it for completeness.

-Barry

-------------------- snip snip --------------------
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: README.LINUX
Url: http://mail.python.org/pipermail/mailman-users/attachments/20020110/a5ba5e26/attachment.pot 
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: README.check_perms_grsecurity
Url: http://mail.python.org/pipermail/mailman-users/attachments/20020110/a5ba5e26/attachment.asc 
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: check_perms_grsecurity.py
Url: http://mail.python.org/pipermail/mailman-users/attachments/20020110/a5ba5e26/attachment-0001.pot