Transitioning to Exchange 2010 e-mail service from intenet based service
For my small business, the e-mails are handled by the domain provide, however I would like to install Small Business Server 2011 and eventually handle all the e-mail by exchange 2010 which is part of Small Business Server 2011. In order to do this, I am setting up SBS2011 to manage the internet domain name directly, meaning that any e-mail sent to myemail@mysite.com will be routed to this server. Since it will take time and testing before go live with the new server, how can I prevent that existing e-mail addresses are not routed to the server yet? However, I will need to send and receive some test e-mails to make sure that everything is configured correctly.
Thank you!
Thank you!
ArneLovius
Configure SBS with the domain name that you want to use, then add a second domain name and use it for testing
Just don't edit your external mx records yet to receive email.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Look few things very Important ....
1. Anonymous Users option needs to be checked on the "Receive connector" for your Server\Users to be able to receive emails from the Internet.
2. Any email that would be UserName@mysite.com or whatever should be listed as "Accepted Domain" in the EMC.
3. There should be "Send Connector" created for routing email to Internet from your domain. If at the moment you are using ISP you can mention it as smarthost but maybe in the near future you might want to consider to change that settings on the SendConnector to route emails using DNS.
Let me know if you have further queries or concerns.
- Rancy
1. Anonymous Users option needs to be checked on the "Receive connector" for your Server\Users to be able to receive emails from the Internet.
2. Any email that would be UserName@mysite.com or whatever should be listed as "Accepted Domain" in the EMC.
3. There should be "Send Connector" created for routing email to Internet from your domain. If at the moment you are using ISP you can mention it as smarthost but maybe in the near future you might want to consider to change that settings on the SendConnector to route emails using DNS.
Let me know if you have further queries or concerns.
- Rancy
If you want a particular email account at your domain to come to the SBS/Exchange you could do this with the supplied POP3 connector and add the accounts as you gain confidence. However, this is not a long term solution. The pop3 connector is meant for just what you are trying to do.
Once you have confidence in the system you just run the wizards in the SBS System Manaager, purchase a certificate, forward port 25 on your rounter to the ip of the SBS, change the MX records and mai will flow automagically.
Once you have confidence in the system you just run the wizards in the SBS System Manaager, purchase a certificate, forward port 25 on your rounter to the ip of the SBS, change the MX records and mai will flow automagically.
@fl_flyfishing: The plan that needs to be setup is for initial testing for mail-flow NOT routing all emails to their system.
@Rancy: I guess cause of the time-lag my answers flowed into yours, is it? Cause what i wrote - pretty much same is written in your post.
Regards,
Exchange_Geek
@Rancy: I guess cause of the time-lag my answers flowed into yours, is it? Cause what i wrote - pretty much same is written in your post.
Regards,
Exchange_Geek
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Let me add to all of the above that with SBS the wizards take care of everything that should be done to receive mail except to forward port 25 and change the MX records. And if you have a compliant router or firewall the wizards will forward port 25 if you allow it to.
All of the advice about tickiing this and that under the hood is unnecessary, and more likely to break things with SBS than not.
The only possible thing that might not allow this to work if the wizards are usesd properly is if the ISP blocks port 25, in which case you will need to use a smart host to send mail.
Two other nuances are static public ip verses dynamic and off site filtering via a third party service.
All of the advice about tickiing this and that under the hood is unnecessary, and more likely to break things with SBS than not.
The only possible thing that might not allow this to work if the wizards are usesd properly is if the ISP blocks port 25, in which case you will need to use a smart host to send mail.
Two other nuances are static public ip verses dynamic and off site filtering via a third party service.
@fl_flyfishing Precisely, which part should break what? I do not see a single recommendation that should break anything on SBS box.
Regards,
Exchange_Geek
Regards,
Exchange_Geek
@fl_flyfishing none of the advise above will break Exchange. Having said that in the areas that we go, if instructions are not followed correctly an admin could click on the wrong things and break exchange (This is part of the reason Microsoft are dropping SBS, as it is becoming more than an in-house, simply follow the wizard OS).
The first part of my instuctions (after the pre-amble) above stated to follow the wizards. However the wizards do not allow for any settings on the anti-spam settings. And with these enabled it will most certainly fail testing as you are going to need to fake senders to bypass the DNS MX (For Testing).
Cheers
Andrew
The first part of my instuctions (after the pre-amble) above stated to follow the wizards. However the wizards do not allow for any settings on the anti-spam settings. And with these enabled it will most certainly fail testing as you are going to need to fake senders to bypass the DNS MX (For Testing).
Cheers
Andrew
@AndrewJDavid: That was the reason precisely I was amused when @fl_Flyfishing commented that this might break something. Yes, something might break if you do not follow the instructions to the core. That is logical, not only to our recommendation - you could do that in real life, try entering some one else' z bank code when you are transferring money in cheque slips- and then the realization dawns - " i should have been careful"
It is an unwritten policy - read, understand and follow, if any doubts - ask.
We wouldn't recommend anything that'll break the environment.
Hence, my question - what part of the recommendation will break what?
Regards,
Exchange_Geek
It is an unwritten policy - read, understand and follow, if any doubts - ask.
We wouldn't recommend anything that'll break the environment.
Hence, my question - what part of the recommendation will break what?
Regards,
Exchange_Geek
ASKER
Thankk you guys, you are amazing.
For clarification, the test server I am working on now is in my house, therefore there is no client pc connected to it other than a future test machine (not there yet). The company is currently serviced by monster.com and the new DNS will be godaddy.com (smart host) so If I am undestanding this process correctly i need:
1. "Ensure that anti spam agents are DISABLED +++ recipient filter is enabled."
2. disable the Antispam features in Exchange managment console, BUT leave recipient filtering turned on.
3. At this point, as you have not redirected your public MX record in DNS to your own server, incoming email will still flow in via your external provider. - I am sure about this one since it is done automatically by the wizard I think, so I think it will be.
4. Open Port 25 on the router
Is this correct?
For clarification, the test server I am working on now is in my house, therefore there is no client pc connected to it other than a future test machine (not there yet). The company is currently serviced by monster.com and the new DNS will be godaddy.com (smart host) so If I am undestanding this process correctly i need:
1. "Ensure that anti spam agents are DISABLED +++ recipient filter is enabled."
2. disable the Antispam features in Exchange managment console, BUT leave recipient filtering turned on.
3. At this point, as you have not redirected your public MX record in DNS to your own server, incoming email will still flow in via your external provider. - I am sure about this one since it is done automatically by the wizard I think, so I think it will be.
4. Open Port 25 on the router
Is this correct?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
1. "Ensure that anti spam agents are DISABLED +++ recipient filter is enabled."
2. disable the Antispam features in Exchange managment console, BUT leave recipient filtering turned on.
Read the following article for how to install the Anti-Spam agents:
http://technet.microsoft.com/en-us/library/bb201691.aspx
then run the command Set-RecipientFilterConfig -RecipientValidationEnable
2. You could manually disable the other Antispam features, if you need - but primarily you'll need to ensure that Recipient Filter enabled for sure.
==> Open Port 25 on router - obvious, cause if your ISP isn't able to connect over port 25, emails will not be able to come in (this isn't related to POP3) and emails won't flow out.
Regards,
Exchange_Geek
ASKER
I've requested that this question be deleted for the following reason:
Not an issue anymore
Not an issue anymore
Disagree with Delete. The fact that it is no longer an issue... does not mean that anything above was not correct and will not be helpfull to a future expert with the same issue.
My recommendation Point split between myself and Exchange_Geek.
cheers
Andrew
My recommendation Point split between myself and Exchange_Geek.
cheers
Andrew
Disagree with Delete. The fact that it is no longer an issue... does not mean that anything above was not correct and will not be helpfull to a future expert with the same issue.
My recommendation Point split between myself and Exchange_Geek.
cheers
Andrew
My recommendation Point split between myself and Exchange_Geek.
cheers
Andrew
ASKER
Since I abbandoned this project, I did not had the opportunity to validate any of the suggestion proposed.
Thank you everyone for the effort.
Thank you everyone for the effort.
ASKER
Good suggestions.