Setting up MailEnable in a corporate environment


How a corporate can configure MailEnable Professional to provide internal and external/internet messaging. The article describes an optimal configuration for MailEnable to provide an integrated messaging for internal users/employees as well as providing web mail access so their mail can be accessed from abroad.


The following table lists the basic services and their implementation for internal and external users. For example: The SMTP Connector will only be configured to allow access those hosts outside the organization.




SMTP Remote internet mail servers (and clients) will be able to send mail to addresses that are locally hosted under the MailEnable environment. SMTP will be used to dispatch mail to remote domains/mail servers, but will not be bound to the Internal Network. i.e. internal mail clients will not be able to configure their Outlook client to send mail via SMTP.


This service will not be available to those accessing MailEnable from the Internet. This service will not be available to those accessing MailEnable from the internal network.


This service will not be available to those accessing MailEnable from the Internet. This service will provide the main mechanism for internal users to access their mail. It is preferred to use HTTPMail rather than POP and SMTP because it stores messages on the server, hence making them available through web mail and simplifying backing up mail data.

Web mail

This service will provide the main mechanism by which users can access their mail via the Internet. Once authenticated, users will be able to access their mail using we browsers. This service will provide a backup mechanism for users to access their mail. The main reason for making web mail accessible directly through the internal network is so that people can access their mail without needing to configure Outlook profiles/accounts.

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:

Service Configuration
SMTP Server Configuration The SMTP Connector should be configured with the default settings but the relay settings for the server should be modified so that it does not allow SMTP Relaying. (In this configuration, relaying through the SMTP server is not necessary). This significantly reduces exposure to spammers/hackers hijacking the SMTP server via security breach. Optionally, you may wish to exclude access to SMTP Services from internal users, you may wish to only bind the SMTP Connector to the Public network interface. There is no real benefit in doing this other than the fact that there is not need to have SMTP accessible through the internal interface.
HTTPMail Configuration HTTPMail is provided as the default protocol for internal users. Users will need to use either Outlook 2002 (or later) or Outlook Express and configure their account to use HTTP for accessing the MailEnable Server. The HTTPMail Service should be configured with the default settings, but should be modified so that it only binds to the internal/private network interface.
Web Mail Configuration Web mail is provided primarily for those users who need to access their mail from outside the company. Users will be able to use a web browser from the Internet to access their mail. The default settings should be accepted for web mail.
POP3 Server Configuration Because internal mail clients are to be configured to use HTTPMail, there is no need to configure POP3 Services under MailEnable. It is therefore recommended that the service be configured to Manual Startup in the Service Control Manager.


MailEnable Quick Start Guide

Product:MailEnable (All Versions)
Class:INF: Product Information
Created:22/09/2002 1:23:00 PM
Revised:Wednesday, May 4, 2016