Make sure that name resolution is fully functional. Configure the external network interface and the internal network interface. Install Windows Server 2008 R2 (I always recommend R2 since it is more efficient and faster than Windows Server 2008) and bring it up to date with the latest hotfixes. Installing the Edge Transport Server is straight forward. Since the Edge Transport Server is not a member of the internal Active Directory, it has no knowledge about for example Accepted Domains or Recipients.
A mechanism needs to be in place to keep the Edge Transport Server up-to-date with information about the internal Active Directory. Outbound messages from the Hub Transport Server are forwarded to the Edge Transport Server and the Edge Transport Server in turn is responsible for the delivery to the Internet. Messages are delivered from the internet to the Edge Transport Server and then sent to the Hub Transport Server.
Location of the Edge Transport ServerĪs I already said, the Edge Transport Server is typically located in the DMZ of the network, between the internet and the internal network.įigure 1 : The test environment with the Edge Server between the Internet and the (internal) Hub Transport Server Since the Edge Transport Server is located in the DMZ it is not a member of the internal Active Directory domain, so some additional configuration is needed.
After processing the message stream, the ‘clean’ stream of SMTP messages is then delivered to the internal Hub Transport Server. This server is typically located in the DMZ where it accepts the SMTP messages coming from the Internet. To implement an anti-spam solution you can implement an Exchange Server 2010 Edge Transport Server. If you would like to be notified of when Jaap Wesselius releases the next part in this article series please sign up to our Real Time Article Update newsletter.
0 kommentar(er)
