No client system on the internal network used POP3 or SMTP to access external network servers. All internal network clients connected to the Exchange 2000 Server using Microsoft Outlook 2000 MAPI client. The Exchange Server received mail for the corporate domain from the spam filtering SMTP mail relay server. The Exchange 2000 Server was located on the same internal network segment as the SMTP mail relay server that did the spam filtering.

We’ve had nothing but excellent results with the Mail essentials spam filter and we’re happy to recommend this solution to the client. We installed GFI software’s Mail essentials for SMTP Gateways 6 on this server. With this in mind, we decided to configure a third SMTP mail relay on the internal network. This guy hated spam with a passion and was willing to do whatever we could to bring it down to an absolute minimum. The client was very interested in minimizing the amount of spam entering his network. An MX record was created for each SMTP mail relay, with Relay 1 having a higher priority than Relay 2. The advantage of putting more than one mail relay server is that you can take one or more of them down and the servers that remain up can handle all the incoming mail for the domain. We decided to put two IIS SMTP mail relay servers on the DMZ segment. We decided to put together a back to back ISA Server DMZ configuration as seen in the figure below: The client had a T1 link to the Internet and he wanted to host his own Internet services, including his own Exchange Server that would receive mail for his domain. You can use this example as a baseline for your own Exchange Server solution and modify it as you see fit. We’ve covered the subject of SMTP Server publishing and mail relay here in the Shinder area before, but I thought it would be a good idea to share with you a recent SMTP relay and spam filtering solution we put together for a client recently. Mail Relay Scenario Using GFI Mail essentials 6 for Gateways

Gfi mailessentials smtp relay