Koozali.org: home of the SME Server

Legacy Forums => General Discussion (Legacy) => Topic started by: Laager on January 24, 2006, 01:36:51 PM

Title: Migrating from SBS 2000 (Exchange) to SME.
Post by: Laager on January 24, 2006, 01:36:51 PM
We are looking to migrate from Exchange on SBS to qmail on SME. Searches have proved inconclusive. Is there a method for exporting an entire user's .pst or .ost to a format that can be dropped into their appropriate SME mail directory so they can access their existing mail via POP3 or the webmail interface?

We want to avoid IMAP as it just confuses users.
Title: Re: Migrating from SBS 2000 (Exchange) to SME.
Post by: CharlieBrady on January 24, 2006, 06:39:10 PM
Quote from: "Laager"
We are looking to migrate from Exchange on SBS to qmail on SME. Searches have proved inconclusive. Is there a method for exporting an entire user's .pst or .ost to a format that can be dropped into their appropriate SME mail directory so they can access their existing mail via POP3 or the webmail interface?

We want to avoid IMAP as it just confuses users.


IMO you are foolish to avoid using IMAP. How do you find it confusing?

If you wish to continue to use POP, then there is no need to migrate .pst file contents to the SME server, the mail client will just pull all the mail items back off the server and into their own storage again. Once that happens, the content will not be available for webmail to access.
Title: Re: Migrating from SBS 2000 (Exchange) to SME.
Post by: Laager on January 24, 2006, 10:09:20 PM
Quote from: "CharlieBrady"
IMO you are foolish to avoid using IMAP.

Yes, that is your opinion.
Quote
How do you find it confusing?

I don't. I said users do.
Quote
If you wish to continue to use POP

I never said we were currently using POP.
Quote
...then there is no need to migrate .pst file contents to the SME server, the mail client will just pull all the mail items back off the server and into their own storage again. Once that happens, the content will not be available for webmail to access.

We know this. It's getting it onto the SME to start with that is the question. You might consider that we want to allow remote POP clients to pull the entire contents of their mail off the server.
Title: Migrating from SBS 2000 (Exchange) to SME.
Post by: girkers on January 25, 2006, 12:56:59 AM
Laager, I with Charlie in that you are very vague in your questioning, but I offer this advice.

On exhange you have an Exchange migration tool which can export all mail to a pst file.  First part sorted.

Set up your SME server, I would suggest IMAP as well, as using POP and leaving email on the server just doesn't make sense (to me anyway). Then use your email client to import the email.
Title: Migrating from SBS 2000 (Exchange) to SME.
Post by: Laager on January 25, 2006, 09:05:21 AM
I really can't understand why we are advised about things that are not asked for. I appreciate the replies but I don't see the point of lecturing us on what people think is better. We have our reasons for the solution we require and it's just not necessary to burden you with those reasons.

In essence, all we want to do is convert the .pst to a format that can be injected into qmail. This much is abundantly clear from the first post.

Not an IMAP import; and for reasons that are irrelevant to the solution.

If someone has a method we would love to hear it. If someone wants to tell us that IMAP is the way to go - we have our reasons for excluding IMAP.
Title: Migrating from SBS 2000 (Exchange) to SME.
Post by: dmac on January 25, 2006, 03:39:46 PM
Don't flame me, but i don't think it's possible to
Quote
inject
a .pst file into Qmail.  Qmail uses the mbox or maildir format for storing mail.
See section 4 in http://www.lifewithqmail.org/lwq.pdf  Microsoft .pst file format is propriatary to Microsoft and doesn't sync well with other mail systems.

Your only option is to create the users on the SME Server and have it respond to your incomming mail.  Then with your existing mail clients (Assuming outlook) connect to the mail server as you normally do with Exchange and donwload all the messages.  

The only reason your receiving the suggestion about imap is with the imap system, the mail is retained on the server.  Makes it much easier to backup and restore.

Microsoft exchange uses a similar method to the imap protocol.  When you utilize the exhange system, the messages still reside on the mail server.

Does this help, but don't flame me,  8-)

Darin MacLachlan
Title: Migrating from SBS 2000 (Exchange) to SME.
Post by: boss_hog on January 25, 2006, 05:24:43 PM
Hey Laager,
I wish I could give you a golden answer, but I haven't found one yet.
What I did come across is some *possible* options to try.
Using a third party e-mail client to do the work for you:
Mozilla's Mail function,
Thunderbird, etc
Here is a link to peek at:

http://tldp.org/HOWTO/Outlook-to-Unix-Mailbox.html

The link actually describes 2 options. First using Mozilla Mail and second is to set-up an IMAP server
 ONLY to migrate the info, and then remove IMAP.
Nothing I found sounded very eligant, but the choices could allow you to step off the MS train.
Good luck.
Joe
Title: Migrating from SBS 2000 (Exchange) to SME.
Post by: brianr on January 29, 2006, 01:09:34 PM
I have done just what you require by "exporting" the mail for each user to a pst file (effectivly copying the data from the exchange server database, to a pst file).  Then moving the mail client (outlook in this case) off the exchange server and onto the SMEServer, then importing the pst file so that the mail is held locally.  If you then want it to be on the server (yes, yes I know YOU don't, but someone esle reading this might), then you can drag and drop the email msgs from the local folder to the imap folder.

Don't forget the address book as well. which requires a similar  approach.
Title: Migrating from SBS 2000 (Exchange) to SME.
Post by: Laager on January 29, 2006, 10:14:23 PM
Brian,

We had considered doing as you suggest and do realise we may have to succumb to the method you describe. However, we are trying to avoid it as we are migrating 300 users and scripting it would be nigh on impossible.