[Mailman-Users] conversion

This question is so broad as to be almost beyond the scope of this
list. I'll just say a few things.

First, I know nothing about Listproc so I can't comment in how Listproc
settings/configurations map to Mailman.

As far as moving lists is concerned, you have three main areas of
concern - list behavior (configuration), membership and archives. As I
said, I can't speak about mapping behavior as I don't know Listproc.
For membership, you need to be able to export a flat file of members
(or two separate files of regular and digest members) in a standard
format like

Users Name <user at example.com>
...

and this can be easily used to populate the Mailman list.

List archives need to be exported as a flat file in *nix mbox format,
and this can be used to create a Mailman archive.

For list addresses, Mailman works in conjunction with an MTA (Sendmail,
Postfix, Exim, etc.) which receives mail sent to a particular domain
or domains and uses aliases or other methods to determine whether the
local part of the address is a mailman address and if so, delivers the
mail to Mailman by piping it to Mailman's mail wrapper.

Each list has a set of addresses. The list posting address for a list
named test in the example.com domain is test at example.com. Every list
also has 9 other associated addresses, in this example they are
test-bounces at example.com, test-admin at example.com (deprecated),
test-owner at example.com, test-request at example.com,
test-confirm at example.com, test-join at example.com,
test-subscribe at example.com, test-leave at example.com and
test-unsubscribe at example.com for various purposes.

If your old domain is going to map to your new machine, you should be
able to keep the same list addresses.

LISTPROC can't deliver its archives in this format (AFAIK), so there
will be munging involved.

Personally, I would ask if someone using a mbox mail app to read the
list (Pine, Thunderbird, Eudora, etc) has a complete archive of the
list, and use their archive file as a basis for importing into
mailman instead of trying to use the INDex and GET file commands in
LISTPROC to access the old archives.

If LISTPROC archive files are anything like LISTSERV notebook files,
I posted a message a couple of months back to the list outlining how
to convert them.

I converted from LISTSERV (though I use LISTPROC for work as well) to
Mailman this year, and the biggest problem is user subscription and
list options though, not archives. I would suspect the same is true
for LISTPROC.

It would help to know a little more about Melinda's list -- its
general settings, number of subscribers, and even if it has
archives. It's pretty easy to translate the results of a REView
command to a mailman list settings unless the list has some very
strange settings.