On Tue, 18 Sep 2007 10:59:38 -0700
Mark Sapiro <[EMAIL PROTECTED]> wrote:
> Raquel wrote:
> >
> >> >1. All of the files under the ./lists/ directory.
> >> >2. All of the files under the ./archives/private/
> >> >directory. 3. ./Mailman/mm_cfg.py
> >> >4. Any other files in the ./archives directory
Raquel wrote:
>
>> >1. All of the files under the ./lists/ directory.
>> >2. All of the files under the ./archives/private/
>> >directory. 3. ./Mailman/mm_cfg.py
>> >4. Any other files in the ./archives directory with in
>> >their names.
>
>When doing this, does a person also tar and move the "mai
On Mon, 29 Jan 2007 12:37:24 -0800
Mark Sapiro <[EMAIL PROTECTED]> wrote:
> >1. All of the files under the ./lists/ directory.
> >2. All of the files under the ./archives/private/
> >directory. 3. ./Mailman/mm_cfg.py
> >4. Any other files in the ./archives directory with in
> >their names.
When
Hank van Cleef wrote:
>I have just moved a 9-year-old list from another installation to mine,
>and have a draft how-to faq on how I did it that isn't quite ready for
>prime time. Since I know there isn't any clear information on this in
>the current mailman FAQ tree, I'll give the salient points
>
> I have the task of setting up a replacement for an existing
> Mailman/Postfix server. I am new to Mailman and I am looking for some
> guidance in this transition. Mailman is currently being used solely as
> a diffusion of information. That is, it does not accept contributions
> from lis
I have the task of setting up a replacement for an existing
Mailman/Postfix server. I am new to Mailman and I am looking for some
guidance in this transition. Mailman is currently being used solely as
a diffusion of information. That is, it does not accept contributions
from list members (re
