At 01:22 PM 4/20/02 -0700, Ellen Spertus wrote:
>Actually, the problem went away when I restarted Mailman. Unless it comes
>back, never mind.
Did you happen to make any code change, like drop in a new cvs build, or patch
something? With 2.1, after you do that, you really need to do a "mailmanct
At 10:55 AM 4/22/02 -0600, you wrote:
>We are going to be changing the name of our Host Name on our Red Hat
>Linux box that Mailman 2.0.8 is running on. I would like to change all
>the lists and configuration for mailman over to this new Host Name. I
>don't want to setup a CNAME in DNS to keep th
We are going to be changing the name of our Host Name on our Red Hat
Linux box that Mailman 2.0.8 is running on. I would like to change all
the lists and configuration for mailman over to this new Host Name. I
don't want to setup a CNAME in DNS to keep the old Host Name accessible.
What steps ar
Can someone out there sanity check my thinking on a possible hole in
Mailman's cookie based authentication.
The scenario I'm concerned with is when Mailman's web GUI is being accessed
by a browser via a caching HTTP proxy server such as Squid, hardly an
uncommon situation these days.
If my un
