From: Mads Martin Joergensen <mmj@mmj.dk>
To: mlmmj@mlmmj.org
Subject: Re: mlmmj <-> ezmlm
Date: Sat, 08 Jan 2005 11:22:59 +0000 [thread overview]
Message-ID: <20050108112259.GX712@mmj.dk> (raw)
In-Reply-To: <41DD4C12.9070509@mikegrice.com>
* Mike Grice <mike@mikegrice.com> [Jan 06. 2005 15:30]:
> Hi there,
>
> I've got a (potentially) tricky problem. We are moving our mail
> system over to Exim from qmail, and one of the major blocks in our way
> is that we have literally hundreds of mailing-lists set up using
> ezmlm. I found out about this project during my search for a
> replacement.
>
> What I want to know, and I'm praying that the answer is yes, is the
> following.
>
> Is there an easy (read: automated) way to convert an ezmlm
> mailing-list and preserve its information to an mlmmj list? If this
> is the case, I will be able to migrate our current lists over to mlmmj
> and all will be good.
There is none yet, but I don't think it will be that hard.
The subscribers will be handled by a bash loop something like this, you
should of course substitute withyour install paths etc.:
for ADDR in `/usr/local/bin/ezmlm-list /var/spool/ezmlm/NAME` ; do
/usr/local/bin/mlmmj-sub -L /var/spool/mlmmj/NAME -a $ADDR
done
It's getting too long since I touched ezmlm lists to remember the
settings flags, but I dunno if it wouldn't be better to sit down reading
TUNABLES and deciding freshly for each new list.
If you manage to create a nice script for this, I'll of course add it to
the contrib/ directory of mlmmj ;-)
--
Mads Martin Joergensen, http://mmj.dk
"Why make things difficult, when it is possible to make them cryptic
and totally illogical, with just a little bit more effort?"
-- A. P. J.
prev parent reply other threads:[~2005-01-08 11:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-06 14:32 mlmmj <-> ezmlm Mike Grice
2005-01-08 11:22 ` Mads Martin Joergensen [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050108112259.GX712@mmj.dk \
--to=mmj@mmj.dk \
--cc=mlmmj@mlmmj.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.