Go Premium for a chance to win a PS4. Enter to Win

x
?
Solved

Exchange 2010 - Prevent internal machines from using as a smart host

Posted on 2012-03-12
4
Medium Priority
?
373 Views
Last Modified: 2012-03-25
The developers in our environment continue to point various servers to our production email server to send test emails.  All of these emails stay internal, so they aren't relaying.  Is there anyway to prevent them from doing this?
0
Comment
Question by:hdfanatic
  • 2
  • 2
4 Comments
 
LVL 43

Expert Comment

by:Adam Brown
ID: 37710764
The IP Address ranges on your Receive Connectors determine which systems can send mail to your Exchange Server. If you remove the internal network's IP range from the list of IP addresses on your Receive Connectors for port 25, it will prevent the Exchange Server from accepting mail from those clients. In order to send mail from an internal server to your exchange server, they'll have to ask for approval.
0
 

Author Comment

by:hdfanatic
ID: 37711188
OK, so I currently have 3 connectors on my Hub/CAS server.  They are as follows:

Client ServerName - Presume this is used by Outlook clients
Default ServerName - Presume this is the connector I need to modify
Relay Connector - This has all the machines that need relay access

My only concern is knowing what other machines are using this Default connector so I can make sure to list every IP needed.  Do my other Exchange servers use this connector (2003 boxes and Edge)?
0
 
LVL 43

Accepted Solution

by:
Adam Brown earned 800 total points
ID: 37711274
The Default one is the one you'd want to modify. You'll want to add all external IP addresses and all internal IP addresses that would communicate with port 25. This does include other exchange servers.
0
 

Author Closing Comment

by:hdfanatic
ID: 37763267
Thanks for the help.
0

Featured Post

Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Are you an Exchange administrator employed with an organization? And, have you encountered a corrupt Exchange database due to which you are not able to open its EDB file. This article will explain all the steps to repair corrupt Exchange database.
Mailbox Corruption is a nightmare every Exchange DBA wishes he never has. Recovering from it can be super-hectic if not entirely futile. And though techniques like the New-MailboxRepairRequest cmdlet have been designed to help with fixing minor corr…
In this Micro Video tutorial you will learn the basics about Database Availability Groups and How to configure one using a live Exchange Server Environment. The video tutorial explains the basics of the Exchange server Database Availability grou…
Exchange organizations may use the Journaling Agent of the Transport Service to archive messages going through Exchange. However, if the Transport Service is integrated with some email content management application (such as an anti-spam), the admin…
Suggested Courses

885 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question