Link to home
Start Free TrialLog in
Avatar of Brian Esser
Brian EsserFlag for United States of America

asked on

Need information on how to transition from an ISP hosted email service to local SBS2003 Exchange Server email service

I have an ISP based email host and a registered domain name that I would like to convert over to the new SBS 2003 Exchange Server I'm putting online.

How do you get email to the new server instead of the ISPs? Or better yet, have the server interact with the ISP email host so the mail is on the web and the local server.

The SBS 2003 is set up with a name like mydomain.local name whereas the registered domain name is like mydomain.com. How does this get reconciled at the server level so mail and remote web services can find the server by name? Or is it better to use the sticky IP address instead?

Thanks,
Brian

ASKER CERTIFIED SOLUTION
Avatar of humeniuk
humeniuk
Flag of Canada image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of Brian Esser

ASKER

Thanks for pointing me in the right direction.

Follow up question: Should I set up pop/smtp and why/not?

Thanks,
Brian
First, thanks for the A.

Whether you should set up pop/smtp depends on what policies you want to implement.  The primary benefit of pop/smtp, I suppose, is that remote users could connect from wherever they are, download their mail, and store it locally.  In most business cases, I would prefer to keep it on the server for the sake of security, centralized backup, etc.  The user could configure their client to leave a copy on the server, of course, but then you get into synchronization issues, etc.  If none of this is relevant to your circumstances, pop/smtp can be a convenient way to go.

On the other hand, OWA provides webmail access to the server that is comparable to using an integrated Exchange/Outlook setup.  It allows the user to access their email wherever there is web access instead of needing a computer with a configured client and keeps everything centralized in the Exchange server.
You're welcome.

Just the information I needed. I agree that because this is a business case we will want to keep it on the server and not leave it to chance with the user configuration using pop/smtp.

You were most helpful.

Thanks,
Brian
Glad to be of some help.  Good luck.