Edward Ned Harvey wrote:
>> Put
>>
>> DEFAULT_BAN_LIST = ['^(?!([EMAIL PROTECTED]))']
>>
>> (or whatever you want) in mm_cfg.py. Then, in order to make it work,
>> find the lines
>>
>> # Ban lists
>> self.ban_list = []
>>
>> in the definition of the InitVars() method in Mailman
Edward Ned Harvey wrote in response to Barry Finkel:
>> What I have done is this - I have about 20 different list template
>> configurations on my Mailman machine. If I want to create a new list
>> of type, say, E1, I do the following as root on the Mailman machine:
>>
>> cp E1.config newli
> > Put
> >
> > DEFAULT_BAN_LIST = ['^(?!([EMAIL PROTECTED]))']
> >
> > (or whatever you want) in mm_cfg.py. Then, in order to make it work,
> > find the lines
>
> Is it true, in general, that there exists a SOME_SETTING variable,
> which can
> be set in the mm_cfg, to set defaults for each of the
> What I have done is this - I have about 20 different list template
> configurations on my Mailman machine. If I want to create a new list
> of type, say, E1, I do the following as root on the Mailman machine:
>
> cp E1.config newlist.config
Hrmmm...
Are you perhaps using an old version o
> Put
>
> DEFAULT_BAN_LIST = ['^(?!([EMAIL PROTECTED]))']
>
> (or whatever you want) in mm_cfg.py. Then, in order to make it work,
> find the lines
Is it true, in general, that there exists a SOME_SETTING variable, which can
be set in the mm_cfg, to set defaults for each of the settings availabl
> Put
>
> DEFAULT_BAN_LIST = ['^(?!([EMAIL PROTECTED]))']
>
> (or whatever you want) in mm_cfg.py. Then, in order to make it work,
> find the lines
>
> # Ban lists
> self.ban_list = []
>
> in the definition of the InitVars() method in Mailman/MailList.py and
> change the second
