The precise implementation of MailEnable is governed by the peripheral infrastructure that you are employing MailEnable services into. For example, an implementation for an organization with multiple network security tiers (i.e. VLANS, Firewalls, Demilitarized Zones) will be more complicated than the scenario outlined below. The precise configuration on if there are other network services configured on the MailEnable server. (i.e. Proxy, DNS, etc). These variations typically would only have a minor impact on the configuration described in this article. This scenario describes an environment where an organization has private and public network interfaces configured on the MailEnable server:

In this scenario, we can see that the external interface only exposes SMTP and web mail services. The SMTP service is used to receive mail for locally hosted domains. It is also responsible for dispatching mail that has been generated by web mail or HTTPMail (Outlook). Web mail access is provided to both internal and external users. Its primary function is to allow roaming users (private and public) to access their mail without needing to configure an Outlook client. HTTPMail is provided for internal users to access their mail using Microsoft Outlook Express/Outlook 2002 or later.

The following table outlines the basic configuration of each of these services: