Assuming you are willing to expose your internal intranet server to the 
outside world, any number of books would work.

This is by no means complete, but the basic concepts / steps are:

   1. Ensure anti-virus and anti-spam protection are up and running (I
      use NOD32 and Ninja)
   2. write down current POP settings of account you are moving away
      from (note the IP address of the incoming mail server)
   3. Make sure DNS lookups are working internally (split DNS vs std DNS)
   4. Set your exchange server to accept mail for the domain name you
      are moving
   5. Set the AD accounts up that are to receive the new mail (do you
      want all current accounts to get this new domain, or just
      specified ones)
   6. Make sure your new shell accounts migrated over have the same
      e-mail address format
   7. Enable protocols you want to use (IMAP, POP3, RPC/HTTP)
   8. Make sure your SMTP routes the new domain name appropriately
      (forwarder vs static)
   9. Program firewall and routers so a publicly-routable IP address
      points to port 25 of your SMTP server
  10.  From new server, make sure you can telnet OUT to an external mail
      server on port 25
  11.  From an EXTERNAL server, make sure you can telnet to your public
      IP address port 25 that you are going to publish
  12. modify your SMTP headers to match the DNS MX record you will make
  13. contact your ISP and have them change your Reverse DNS lookups to
      the DNS MX record you will make
  14. change MX record(s) to new public IP address (for externally
      hosted DNS) to begin process of routing new mail; modify internal
      DNS MX record if using split DNS
  15. use web tools to confirm DNS changes are correct
  16. publish new SPF records
  17. set up your clients to receive mail from the new location
  18. configure a secondary POP account to check mail from the old
      location (using the IP of the old mail server); keep this on for a
      few days while DNS propagates.
  19. set up external clients (Windows / PDA / etc) to use RPC/HTTP if
      necessary
  20. decide if you want to expose IIS to the outside world and publish
      OWA; generate SSL certificate if necessary

Klint Price
Arizona IT Pro
877.879.9535


David W. McSpadden wrote:
> I have an Exchange 2003 server for my intranet.  I pay someone else $1 
> an account to host my Internet email.
> I would like to cut out the middle man.  What books or links can I 
> read to become that guy that hosts his own Internet/intranet email??
>  
>


~ Upgrade to Next Generation Antispam/Antivirus with Ninja!    ~
~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm>  ~

Reply via email to