Todd,
What type of email client are you using? Depending on
the client, you may want to do most of the migration
work on the client-side. What I'm about to explain
would work for a client like Outlook that can have
multiple Mail accounts configured for the same
profile. As a possible (though not ideal) workaround
to the new mail delivery issue, you can:
1) Bring your IMail server online
2) Configure all of your clients with an additional
Mail service to send/receive mail through the Imail
server, configuring the IMail server as the primary
but keeping the old mail service as well until their
mail is off of the old server
3) Change your MX record to point to the new IMail
server, so that all new mail will be delivered to the
Imail server
4) Migrate individual users off of the Pegasus and
Mercury servers at your own convenience.
I've been through a couple major mail migrations, and
each time we've decided on a migration process like
the one described above, because people couldn't be
without their email for even a short time and it's
really transparent to them. The main difference
between the steps above and what I've done in the past
is that we've worked with an IMA, a machine that
accepts all inbound mail and redelivers it to the
appropriate server based on the address/username.
This allowed users to be hosted at different mail
servers during the migration without loss of service.
Using the IMA, you must still migrate each user one at
a time, but you'll only configure the client once
(while simultaneously having an administrator at the
IMA change the pointer for the destination server of
that address). If you can't afford to set up an IMA,
it will be a huge pain to configure the clients of all
300 users twice using the steps I mentioned above, but
at least it will be transparent for the users.
John
--- Todd Ryan <[EMAIL PROTECTED]> wrote:
> I haven't found anything in my IMail list mail or
> the KB about doing this.
> I have about 300 users on Mercury 1.47 and Pegasus
> Mail 3.1 for Windows.
> All is running on Netware in Bindery mode.
>
> I am migrating to IMail and have figured out
> everything except how to get
> the users' mailboxes from the format Mercury/Pegasus
> uses to the IMail
> format. I can't assume that they will pop all their
> mail from the old
> server before I do the migration so I HAVE to get
> their new mail messages
> from the Mercury server to the IMail server so they
> can POP it after the
> upgrade.
>
> I want to move everyone's NEW mail to the IMail
> server so the first time the
> POP to it, they'll pull down everything the hadn't
> downloaded from the OLD
> server. Figuring out the Pegasus/Mercury mail
> format is pretty easy. But I
> can't get a handle on the IMail mailbox format. I
> didn't find anything in
> the KB about it.
>
> Can anyone answer either of the following questions
> for me?
>
> 1) Is there any utility that will convert unread
> mail messages from Mercury
> to IMail?
>
> if not...
>
> 2) Is the format of the MAIN.MBX file documented
> anywhere? I don't think I
> can just create the MAIN.MBX with all the files in
> it, can I? How do
> MAIN.SRT and MAIN.UID come into play? They're
> binary files so I don't think
> I'll be able to create them too easily if I should
> need them.
> Thanks!
>
> --Todd.
>
>
>
>
> Please visit
> http://www.ipswitch.com/support/mailing-lists.html
> to be removed from this list.
>
> An Archive of this list is available at:
>
http://www.mail-archive.com/imail_forum%40list.ipswitch.com/
__________________________________________________
Do You Yahoo!?
Yahoo! Auctions - buy the things you want at great prices
http://auctions.yahoo.com/
Please visit http://www.ipswitch.com/support/mailing-lists.html
to be removed from this list.
An Archive of this list is available at:
http://www.mail-archive.com/imail_forum%40list.ipswitch.com/
