Exchange 2010, restricting mail from just specified IP addresses
I have just migrated to Exchange 2010 (SBS2011) from Excahnge 2000 (SBS2003). I have an external Spam mail filter that will work much better if I can restrict ALL external mail from only certain specified IP addresses. I cannot find where I
can accomplish this. Can anyone help with that task?
March 4th, 2011 7:36am
The best way to do it is on the firewall, restrict the SMTP traffic there, rather than further back on the Exchange server. That can also ensure that the restrictions don't cause problems in the future.
If you must set it in Exchange because of the limitations of your firewall, then it is set on the Default Receive Connector. It will be set to all IP addresses by default, which will have to be replaced by the IP addresses that you need to restrict it to.
Simon.Simon Butler, Exchange MVP
Blog |
Exchange Resources | In the UK?
Hire Me.
Free Windows Admin Tool Kit Click here and download it now
March 4th, 2011 12:51pm
Hi gcrab,
Any updates?
Frank Wang
TechNet Subscriber Support
in forum
If you have any feedback on our support, please contact
tngfb@microsoft.com
Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
March 7th, 2011 1:07am
I thought I had replied earlier, sorry. I was asking why Simon thought that configuring the Default Recieve Connector would 'cause problems in the future'??
I have a firewall and can setup some rules there, but it is easier and more straight forward to configure Exchange. I guess it is what I a more familiar with.
Give me your thoughts.
Free Windows Admin Tool Kit Click here and download it now
March 7th, 2011 7:46am
Restrictions get forgotten about.
You try to add an additional server, migration, send an application notification email to that server etc. They don't work as expected because you have forgotten about the restriction. Or you aren't even working there and the replacement doesn't know about
the restriction.
Firewalls are designed to restrict traffic, which is why it is best to place restrictions at that point, rather than at the application.
Simon.Simon Butler, Exchange MVP
Blog |
Exchange Resources | In the UK?
Hire Me.
March 7th, 2011 10:12am
Good point Simon, I agree.
Free Windows Admin Tool Kit Click here and download it now
March 7th, 2011 10:24am