Setting up exchange server at home
Guest
Posts: n/a
What is the best method to get the most out of playing about with it? Just set it up to use existing pop3/imap accounts or buy a domain name with email and go the whole hog?
With the latter anyone have any recomendations who to go with?
Need to brush up on my exchange 2003 skills, not used for ages and then look at exchange 2007 which i've never touched.
With the latter anyone have any recomendations who to go with?
Need to brush up on my exchange 2003 skills, not used for ages and then look at exchange 2007 which i've never touched.
I'd be tempted to go straight for the demo version of 2010 its quite a different beast compared to the others.
I'm not sure the "full business" version of exchange (ie not SBS) supports pull pop3.
I'm not sure the "full business" version of exchange (ie not SBS) supports pull pop3.
Guest
Posts: n/a
Thanks for the reply, need to do 2003 first before going to later versions. This is self learning (refresh) for work as upgrade time will be along soon. Pretty much forgotten all my exchange mcp stuff so going over it again plus pretty much all exchange stuff at work the last time I did any has been admin/maintenance as opposed to fresh installs.
2003 does do pop3.
2003 does do pop3.
I think setting up a domain name and pointing the mx records to your house might be over kill! Imagine the spam down your net connection.
I would stick with pop collection and build out the servers as virtual machines. Your choice on the vm technology you choose, I use VMware ESX/vSphere servers. You can then setup multiple servers, routing groups/connectors etc..
Are you going for the full fat version? Remember the domain controllers, forest prep and all that...
I would stick with pop collection and build out the servers as virtual machines. Your choice on the vm technology you choose, I use VMware ESX/vSphere servers. You can then setup multiple servers, routing groups/connectors etc..
Are you going for the full fat version? Remember the domain controllers, forest prep and all that...
Guest
Posts: n/a
Thanks, yep already have full ha/drs esx get up with virtual san with dc's and exchange server built today. Wanted the full get up as need it to be as close to a business setup as possible. Only when I have the full lot will I be happy then i'll start clustering them 
So what do you recomend with the domain name and mx records? It's this bit i've never got my head around as the external networking side gets me in a :s If I buy a domain name it's not going to provide me with unlimited email addresses such as a business has? I wanted to set the AD/exchange up with 100 accounts/mailboxes and spread them over stores etc.
So apart from buying a domain name what else am I going to need to get email directly to my exchange server. Oh and I only have 1 static ip address which is on my router, can I just NAT through to my exchange server or is that going to need a static address to?
Ther spam thing isn't an issue as 1) it wont be on all day and 2) this is just to say i've done it and played about with and not a long term setup.

So what do you recomend with the domain name and mx records? It's this bit i've never got my head around as the external networking side gets me in a :s If I buy a domain name it's not going to provide me with unlimited email addresses such as a business has? I wanted to set the AD/exchange up with 100 accounts/mailboxes and spread them over stores etc.
So apart from buying a domain name what else am I going to need to get email directly to my exchange server. Oh and I only have 1 static ip address which is on my router, can I just NAT through to my exchange server or is that going to need a static address to?
Ther spam thing isn't an issue as 1) it wont be on all day and 2) this is just to say i've done it and played about with and not a long term setup.
You would need a domain name and someone to host it for you. They would also need to allow you to create a mx record or create one for you which will point at your home static ip. This will allow mail destined for your domain to know which server on what ip to send it to. Unlimited addresses. You exh server will sort it out...
Yes you can NAT it. Port forward the correct ports from the external connection to the internal ip of your exchange server.
Don't open relay
Yes you can NAT it. Port forward the correct ports from the external connection to the internal ip of your exchange server.
Don't open relay
Guest
Posts: n/a
Nice one thanks. I'll have a look tomorrow where to get a domain/host from. Thought NAT would work, anyway got my enormous Exchange 2003 book out for a bit of light reading
Already coming back to me like of course the number of addresses will be unlimited, it's the domain the mx record points to and doesn't matter about the bit in front of domain address 
The whole reason i'm doing this is becasue I was wintel BAU support and now am Wintel projects and have forgotten so much since stopping BAU support. So building my own environment from scratch is my way of trying to get back some of the technical BAU stuff.
at open relay, no definitely wont be allowing that!
Already coming back to me like of course the number of addresses will be unlimited, it's the domain the mx record points to and doesn't matter about the bit in front of domain address 
The whole reason i'm doing this is becasue I was wintel BAU support and now am Wintel projects and have forgotten so much since stopping BAU support. So building my own environment from scratch is my way of trying to get back some of the technical BAU stuff.
at open relay, no definitely wont be allowing that!
Last edited by Bravo2zero_sps; Jun 24, 2010 at 11:20 PM.
Trending Topics
Guest
Posts: n/a
Got a domain for £1.03 lol and changed isp to staic ip for another fiver a month so all sorted now. Was being a dummy above about the email addresses 
Using 123-reg and nice control panel allowing setup of mx records etc. Just got to set it all up now!

Using 123-reg and nice control panel allowing setup of mx records etc. Just got to set it all up now!
you need to make sure you install IIS as this has the smtp service
it is not in Exchange
you will also need to set a recipient policy unless your AD has a FQDN
(although you will still be able to send mail)
you can test your PAT by telnetting the public IP address on port 25
telnet 81.X.X.X 25 - and you will see the below response
220 server1.XXXXXX.local Microsoft ESMTP MAIL Service, Version: 6.0.3790.1830
ready at Wed, 30 Jun 2010 20:40:10 +0100
you can also then use native SMPT commands to test internal mail delivery and test your connector for relay -without the need to set up mx records etc
and yes it does POP and IMAP
it is not in Exchange
you will also need to set a recipient policy unless your AD has a FQDN
(although you will still be able to send mail)
you can test your PAT by telnetting the public IP address on port 25
telnet 81.X.X.X 25 - and you will see the below response
220 server1.XXXXXX.local Microsoft ESMTP MAIL Service, Version: 6.0.3790.1830
ready at Wed, 30 Jun 2010 20:40:10 +0100
you can also then use native SMPT commands to test internal mail delivery and test your connector for relay -without the need to set up mx records etc
and yes it does POP and IMAP
Last edited by hodgy0_2; Jun 30, 2010 at 08:45 PM.
Guest
Posts: n/a
at PBXCheers Hodgy. Already got an exchange server installed but going to rebuild the lot to the new domain bought today. Got a build vm sitting there which I use for cloning so shouldn't take too long to start again.
you can also then use native SMPT commands to test internal mail delivery and test your connector for relay -without the need to set up mx records etc
personally I would separate my internal and external name spaces
i.e. my AD domain would be company.local -- or even just ad.local
this is completely (technically speaking) divorced from the email domain (i know several very large corp's who's AD is called something like ad.local -- it makes mergers, re-brands and acquisitions much much easier
so you would have the email - lets say administrator@yourdomain.com delivered -- by Exchange to a user, who's UPN is administrator@ad.local
(this is where a recipient policy comes in)
i.e. my AD domain would be company.local -- or even just ad.local
this is completely (technically speaking) divorced from the email domain (i know several very large corp's who's AD is called something like ad.local -- it makes mergers, re-brands and acquisitions much much easier
so you would have the email - lets say administrator@yourdomain.com delivered -- by Exchange to a user, who's UPN is administrator@ad.local
(this is where a recipient policy comes in)
yep -- sometime the confusion comes from the name Domain
the AD Domain is a completely different entity from a DNS Domain (and an Email Domain)
their is no reason why they have to be the same
having them the same makes designing DNS a little easier (although you could argue less secure)
the AD Domain is a completely different entity from a DNS Domain (and an Email Domain)
their is no reason why they have to be the same
having them the same makes designing DNS a little easier (although you could argue less secure)
Last edited by hodgy0_2; Jul 1, 2010 at 10:34 AM.
yes -- if you have a DNS control panel -- provided by your ISP that allows you to modify/create DNS records for your Domain (FDQN DNS Domain - not AD) all you do is create a A host record that matches your public IP address - say mail.yourdomain.com
then set an MX record that maps to mail.yourdomain.com
then on your router set a Port Address Translation (PAT) that maps port 25 on you public IP address to Port 25 on the private IP address
some ISP's can be funny about directing port 25 traffic to a residential IP address btw
to test PAT-- from a remote IP address telnet your public IP on port 25
to test DNS telnet mail.yourdomain.com on port 25
both should expose the Exchange SMTP service
to test your MX record - use NSLOOKUP
from within NSLOOKUP
type the commands - one on each line
set query=MX
yourdomain.com
it will then query (your DNS server) for the MX record for yourdomain.com
see below for an example
> set query=MX
> microsoft.com
Server: ukhddcfs2k3-1.mydnsserver.local
Address: 10.254.118.19
Non-authoritative answer: (because I did not query Microsofts DNS server)
microsoft.com MX preference = 10, mail exchanger = mail.messaging.microsoft.com
mail.messaging.microsoft.com internet address = 65.55.88.22
>
now type telnet 65.55.88.22 25
all the above sets up the infrastructure that allows delivery of email destined for anyone@yourdomain.com to hit the Exchange SMTP service
(the internet is not concerned with anything before the @ sign -- but your exchange server is)
so you have to tell exchange how to handle mail that will hit it's SMTP service destined for @yourdoman.com
otherwise it will not deliver it (unless offcourse you have named you AD yourdomain.com which is a bad idea imo) -- this is done in recipient policies
then set an MX record that maps to mail.yourdomain.com
then on your router set a Port Address Translation (PAT) that maps port 25 on you public IP address to Port 25 on the private IP address
some ISP's can be funny about directing port 25 traffic to a residential IP address btw
to test PAT-- from a remote IP address telnet your public IP on port 25
to test DNS telnet mail.yourdomain.com on port 25
both should expose the Exchange SMTP service
to test your MX record - use NSLOOKUP
from within NSLOOKUP
type the commands - one on each line
set query=MX
yourdomain.com
it will then query (your DNS server) for the MX record for yourdomain.com
see below for an example
> set query=MX
> microsoft.com
Server: ukhddcfs2k3-1.mydnsserver.local
Address: 10.254.118.19
Non-authoritative answer: (because I did not query Microsofts DNS server)
microsoft.com MX preference = 10, mail exchanger = mail.messaging.microsoft.com
mail.messaging.microsoft.com internet address = 65.55.88.22
>
now type telnet 65.55.88.22 25
all the above sets up the infrastructure that allows delivery of email destined for anyone@yourdomain.com to hit the Exchange SMTP service
(the internet is not concerned with anything before the @ sign -- but your exchange server is)
so you have to tell exchange how to handle mail that will hit it's SMTP service destined for @yourdoman.com
otherwise it will not deliver it (unless offcourse you have named you AD yourdomain.com which is a bad idea imo) -- this is done in recipient policies
Last edited by hodgy0_2; Jul 1, 2010 at 01:41 PM.
Guest
Posts: n/a
Cheers Hodgy - again! Yep already set up the mx record on the dns control panel of 123-reg for my domain name as takes 24 hours plus to replicate so first thing I did so would be ready to use once i'm set. Sorted the port 25 issue with my isp by paying for static ip so thats in place too. I can do the port forwarding on my router no issues as already have several rules setup.
The rest i'll do once got everything working including the recipient policy which will hopefully be over the weekend.
The rest i'll do once got everything working including the recipient policy which will hopefully be over the weekend.
Guest
Posts: n/a
The admin stuff I'm fine with used exmerge loads before. The problem has been never getting to set stuff up from scratch at work as core infrastructure has always been in place. No test/sandbox environment at work for us to play in so had to get my own at home. Plus had all BAU work taken off us and put off shore which I really miss.
Also only did up to MCSA with messaging (which shows how bad my
memory is having to ask about setting exchange up!) in my exams so using the home get up to help get the last 3 mcps for MCSE at some stage.
Also only did up to MCSA with messaging (which shows how bad my
memory is having to ask about setting exchange up!) in my exams so using the home get up to help get the last 3 mcps for MCSE at some stage.
Last edited by Bravo2zero_sps; Jul 5, 2010 at 07:17 PM.
Thread
Thread Starter
Forum
Replies
Last Post
Mattybr5@MB Developments
Full Cars Breaking For Spares
28
Dec 28, 2015 11:07 PM









