MS Exchange 2003 -> SurgeMail (OS X)

Hi,

Im doing an MS Exchange 2003 to SurgeMail conversion.  (and
for your  
information no I didn't set the exchange server, Im coming
in after  
the fact.  And further more, this is MS Small Business
Server 2003.)

I know the answer Im going to get but I don't think that
answer is  
practical given the mailbox sizes involved.

I want to move my users from Exchange to SurgeMail, my silly
question  
is by using the migration mode for SurgeMail that would be
practical  
in most cases, however in this case, its not. I've got to
move well  
over a gig of mail PER USER (and Ive got 55 users, and this
is a  
financial services company, and all of their mail MUST BE
KEPT even  
if its 'private or personal' mail for federal reasons).

Ive seen some references in the archives to just moving the
mail  
folders but as Ive discovered (the hardway) that there are
no  
mailfolders in exchange, but everything is kept in a
database.  Which  
I can see now why this thing is deathly slow!

So before I do anything I know I need to back up the
exchange server,  
I'll look online to find out how to do that, but any
instructions or  
quick instructions you folks can give me would be great.

Next to my very silly question is HOW would you folks move
mail for  
these users when each user has well over a gig of mail, and
in some  
cases exceeding 3 gigs! ?  SurgeMail will choke on that...or
so I  
believe.

Any help, and please be clear in your instructions, step by
step is  
helpful.

Thanks ahead of time...

M i l e s.

m i l e s wrote:
> Hi,
>
> Im doing an MS Exchange 2003 to SurgeMail conversion.
(and for your
> information no I didn't set the exchange server, Im
coming in after
> the fact. And further more, this is MS Small Business
Server 2003.)
>
> I know the answer Im going to get but I don't think
that answer is
> practical given the mailbox sizes involved.
>
> I want to move my users from Exchange to SurgeMail, my
silly question
> is by using the migration mode for SurgeMail that would
be practical
> in most cases, however in this case, its not. I've got
to move well
> over a gig of mail PER USER (and Ive got 55 users, and
this is a
> financial services company, and all of their mail MUST
BE KEPT even if
> its 'private or personal' mail for federal reasons).
>
> Ive seen some references in the archives to just moving
the mail
> folders but as Ive discovered (the hardway) that there
are no
> mailfolders in exchange, but everything is kept in a
database. Which I
> can see now why this thing is deathly slow!
>
> So before I do anything I know I need to back up the
exchange server,
> I'll look online to find out how to do that, but any
instructions or
> quick instructions you folks can give me would be
great.
>
> Next to my very silly question is HOW would you folks
move mail for
> these users when each user has well over a gig of mail,
and in some
> cases exceeding 3 gigs! ? SurgeMail will choke on
that...or so I believe.
>
> Any help, and please be clear in your instructions,
step by step is
> helpful.
>
> Thanks ahead of time...
>
> M i l e s.
>
I think Surge will suffer from the 2gig limit as other mail
servers do
that don't use a database approach to storeage. But I know
that you have
to keep the old email. A couple of approaches:

1) segegrate the email on the client into seperate personal
folders by
date. If it's in a PST, it's seperate file(but even PST's
are limited to
2gig). You could then create seperate folders on the Surge
server to
push that email back up to Surge

2)Put those PST on a file server and don't import them into
Surge. By
putting them on a file server, they should be backed up and
'safe' for
later retreival. but still availible for Outlook users and
the regulators.

There are other ways to keep email for regulartory reasons
than piling
it into each users email. And what would prevent the end
user from
deleting it? That means their method won't qualify as
archiving for
regulatory purposes...

I have not looked to see if Surge has a lawfull interecpt
feature that
would work for archiving email(and would be outside the
user's ability
to muck with).

Lyle

Hi,

You would enable IMAP at the exchange server - you can do it
under ther
server - protocol settings in the exchange system manager.

Then you set surgemail up to migration mode ant write the
exchange
servers ip into the imap field.

The you start a e-mail client with IMAP support and connects
to
surgemail with imap and the usernames and password. You have
to set the
strip domain option in the migration page becourse that the
exchange
server dossent uses domains in the user names.

When you have connected the surgemail it creates the user
and starts
migrating mails to surgemail.

If thay have public folders on the exchange server, then you
have to
start a outlook client and export the public folders to .pst
files. 

If you have any more questions, then let me know.

 
Med venlig hilsen / Kind regards
JDM IT A/S
 
Emil Werbes Hempel
 

-----Oprindelig meddelelse-----
Fra: m i l e s [mailto:magicmilesgmail.com] 
Sendt: 28. december 2006 03:00
Til: surgemail-listnetwinsite.com
Emne: [SurgeMail List] MS Exchange 2003 -> SurgeMail (OS
X)

Hi,

Im doing an MS Exchange 2003 to SurgeMail conversion.  (and
for your
information no I didn't set the exchange server, Im coming
in after the
fact.  And further more, this is MS Small Business Server
2003.)

I know the answer Im going to get but I don't think that
answer is
practical given the mailbox sizes involved.

I want to move my users from Exchange to SurgeMail, my silly
question is
by using the migration mode for SurgeMail that would be
practical in
most cases, however in this case, its not. I've got to move
well over a
gig of mail PER USER (and Ive got 55 users, and this is a
financial
services company, and all of their mail MUST BE KEPT even if
its
'private or personal' mail for federal reasons).

Ive seen some references in the archives to just moving the
mail folders
but as Ive discovered (the hardway) that there are no
mailfolders in
exchange, but everything is kept in a database.  Which I can
see now why
this thing is deathly slow!

So before I do anything I know I need to back up the
exchange server,
I'll look online to find out how to do that, but any
instructions or
quick instructions you folks can give me would be great.

Next to my very silly question is HOW would you folks move
mail for
these users when each user has well over a gig of mail, and
in some
cases exceeding 3 gigs! ?  SurgeMail will choke on that...or
so I
believe.

Any help, and please be clear in your instructions, step by
step is
helpful.

Thanks ahead of time...

M i l e s.

Hi Lyle,

Outlook before Outlook 2003 does have the 2 gig limit -
Outlook 2003
have no limit. Please notice that you must run at NTFS for
this to be
true - FAT32 have limitations in the maximum files size (2
gig)

 
Med venlig hilsen / Kind regards
JDM IT A/S
 
Emil Werbes Hempel
 

-----Oprindelig meddelelse-----
Fra: Lyle Giese [mailto:lylelcrcomputer.info] 
Sendt: 28. december 2006 04:02
Til: surgemail-listnetwinsite.com
Emne: Re: [SurgeMail List] MS Exchange 2003 -> SurgeMail
(OS X)

m i l e s wrote:
> Hi,
>
> Im doing an MS Exchange 2003 to SurgeMail conversion.
(and for your 
> information no I didn't set the exchange server, Im
coming in after 
> the fact. And further more, this is MS Small Business
Server 2003.)
>
> I know the answer Im going to get but I don't think
that answer is 
> practical given the mailbox sizes involved.
>
> I want to move my users from Exchange to SurgeMail, my
silly question 
> is by using the migration mode for SurgeMail that would
be practical 
> in most cases, however in this case, its not. I've got
to move well 
> over a gig of mail PER USER (and Ive got 55 users, and
this is a 
> financial services company, and all of their mail MUST
BE KEPT even if

> its 'private or personal' mail for federal reasons).
>
> Ive seen some references in the archives to just moving
the mail 
> folders but as Ive discovered (the hardway) that there
are no 
> mailfolders in exchange, but everything is kept in a
database. Which I

> can see now why this thing is deathly slow!
>
> So before I do anything I know I need to back up the
exchange server, 
> I'll look online to find out how to do that, but any
instructions or 
> quick instructions you folks can give me would be
great.
>
> Next to my very silly question is HOW would you folks
move mail for 
> these users when each user has well over a gig of mail,
and in some 
> cases exceeding 3 gigs! ? SurgeMail will choke on
that...or so I
believe.
>
> Any help, and please be clear in your instructions,
step by step is 
> helpful.
>
> Thanks ahead of time...
>
> M i l e s.
>
I think Surge will suffer from the 2gig limit as other mail
servers do
that don't use a database approach to storeage. But I know
that you have
to keep the old email. A couple of approaches:

1) segegrate the email on the client into seperate personal
folders by
date. If it's in a PST, it's seperate file(but even PST's
are limited to
2gig). You could then create seperate folders on the Surge
server to
push that email back up to Surge

2)Put those PST on a file server and don't import them into
Surge. By
putting them on a file server, they should be backed up and
'safe' for
later retreival. but still availible for Outlook users and
the
regulators.

There are other ways to keep email for regulartory reasons
than piling
it into each users email. And what would prevent the end
user from
deleting it? That means their method won't qualify as
archiving for
regulatory purposes...

I have not looked to see if Surge has a lawfull interecpt
feature that
would work for archiving email(and would be outside the
user's ability
to muck with).

Lyle

On Wed, 2006-12-27 at 19:59 -0600, m i l e s wrote:
> Next to my very silly question is HOW would you folks
move mail for  
> these users when each user has well over a gig of mail,
and in some  
> cases exceeding 3 gigs! ?  SurgeMail will choke on
that...or so I  
> believe.

I'm not sure why it would choke on that. Over the last two
weeks I've
migrated about 200GB of mail to Surgemail. It didn't choke
on any of
that. Some of the accounts were as large as 800MB, and
Surgemail didn't
hiccup. In a previous migration we had one user who had over
1GB and
Surgemail handled that as well.

The 2GB limit that others have mentioned is a filesystem
limitation on
the size of a single file. Surgemail doesn't store the
mailbox in a
single file, so that's not a problem. What is a problem is
that it
stores all the mail as separate files in a single directory
(per
folder), which can get really slow for lots of files. The
new NDB format
is meant to alleviate that.

What we've found is the most reliable method for doing
migrations is to
fire them off manually with tellmail imap_migrate. In our
current
transition that was possible because of some LDAP magic that
we've got
going on and we were able to move users one at a time. It
does require
that you know all the users' passwords which may not be
possible.

Corey