Mark Sapiro said:
>
> In your case, I'd recommend starting with just the site list on the new
> system and then copying the lists/ and archives/ directories.
>
> The new Mailman will automatically translate the old format files in
> lists/ as they are used.
>
Well, damn. That was too easy. I w
Mark Sapiro wrote:
> Dwight Tovey wrote:
>
>>Mark Sapiro said:
>>
>>>The preferred method is to move the lists/listname/* files over, rather
>>>than moving the list configuration and membership as you did.
>>>
>>
>>Not a problem. I'm still running on the old system, so I can blow
>>everything awa
Dwight Tovey wrote:
>
>Mark Sapiro said:
>>
>> The preferred method is to move the lists/listname/* files over, rather
>> than moving the list configuration and membership as you did.
>>
>
>Not a problem. I'm still running on the old system, so I can blow
>everything away on the new system and sta
Mark Sapiro said:
> Dwight Tovey wrote:
>>
>>I have some lists running on a system with Mailman 2.0.13. I have
>>installed Mailman 2.1.6 on a new system and I would like to move the
>>existing lists to the new system. This will be a replacement system, so
>>the domain names will remain the same.
Dwight Tovey wrote:
>
>I have some lists running on a system with Mailman 2.0.13. I have
>installed Mailman 2.1.6 on a new system and I would like to move the
>existing lists to the new system. This will be a replacement system, so
>the domain names will remain the same.
>
>I used config_list on
Hello all
I have some lists running on a system with Mailman 2.0.13. I have
installed Mailman 2.1.6 on a new system and I would like to move the
existing lists to the new system. This will be a replacement system, so
the domain names will remain the same.
I used config_list on the old system to
