> in indymedia (http://indymedia.org) and sindominio
> (http://sindomino.net) we saw the necessity to protect the admin part
> of mailman (above all the password transmission) with a ssl
> connection.
We protect all of mailman with an Apache rewrite rule. This is probably
overkill for public arch
On Fri, 2003-05-30 at 21:22, Ernest Christley wrote:
> I've been trying to set up a list behind my firewall on the local
> network. The machine hosting mailman uses 192.168.0.2 as a static IP,
> but the world sees me as ernest.isa-geek.org, the DNS entry I got
> through dyndns.org.
>
> If you
On Mon, 2003-06-09 at 18:55, Donn Cave wrote:
> I added a parameter to ScriptURL(..., upgrade=0) and a couple of
> functions to deal with the protocol part of the URL (http vs. https.)
> The upgrade parameter indicates that the URL must be https. And then
> I had to change a few modules other tha
On Tue, 2003-06-10 at 15:22, Marisa Riviere wrote:
> It seems that I find the answer to the first part of my question.
> I should include the line:
> DEFAULT_URL_PATTERN = 'http://%s/mail_man/'
> in mm_cfg.py as well. Please tell me if I need some thing else.
Yes, this will work for new lists, b
It seems that I find the answer to the first part of my question.
I should include the line:
DEFAULT_URL_PATTERN = 'http://%s/mail_man/'
in mm_cfg.py as well. Please tell me if I need some thing else.
I still need to know how to convert existing lists from one
version to other (2.0.8 to 2.1.2) a
I am updating mailman to a new version but until I can test
all the changes I like to run two versions of the program.
I am working in a SuSE Linux 8.0 system.
For the old versions I used the default settings and defined:
ScriptAlias /mailman/ /usr/lib/mailman/cgi-bin/
Alias
