On 8/27/2004 5:31, "Kai Schaetzl" <[EMAIL PROTECTED]> wrote:
>> It's not that simple. SOME of the things you can put into mm_cfg.py apply
>> only to new lists.
>
> You mean NOT only? That's exactly what makes it so confusing, the overall
> changes which apply to all lists change immediately, the
John W. Baxter wrote on Thu, 26 Aug 2004 16:14:15 -0700:
> It's not that simple. SOME of the things you can put into mm_cfg.py apply
> only to new lists.
You mean NOT only? That's exactly what makes it so confusing, the overall
changes which apply to all lists change immediately, the others don
On 8/26/2004 15:32, "Kai Schaetzl" <[EMAIL PROTECTED]> wrote:
> Yes, it's there, sorry for the unnecessary question. It wasn't quite clear
> to me that mm_cfg.py changes are only for new lists. I suggest adding
> something about that to the comments in mm_cfg.py.
It's not that simple. SOME of th
Mark Sapiro wrote on Thu, 26 Aug 2004 14:11:29 -0700:
> Did the lists exist when you set up mm_cfg.py?
Yes, I always create mailman as the first list, usually I don't log in,
but make my changes to mm_cgf.py and then add other lists from a template.
I suppose that's why I never noticed the http
Kai Schaetzl wrote:
>We use only https:// for web interface access and in the past I changed
>the URL_PATTERN in mm_cfg.py and everything was fine. That worked until
>2.1.5 RC1. Now I have set up a fresh 2.1.5 on a new machine and can't make
>it to work there. Either I overlook something very o
We use only https:// for web interface access and in the past I changed
the URL_PATTERN in mm_cfg.py and everything was fine. That worked until
2.1.5 RC1. Now I have set up a fresh 2.1.5 on a new machine and can't make
it to work there. Either I overlook something very obvious or 2.1.5
ignores
