Before starting this procedure, complete the initial Mail Gateway setup steps.

When using Telligent Community with Exchange, we recommend having your site running on a subdomain from your main email accounts - for instance, This allows you to easily delegate control for the entire subdomain to Mail Gateway - without need for extensive configuration.

In order to use addresses with the main domain, the only route is to create accounts for each of the addresses you'll need, and then configure Mail Gateway to download messages from them. You cannot use aliases because Outlook will often override the alias address with the main account address, causing undesired behavior.

Configure DNS

Within your network, you will need to create a DNS entry for the subdomain on which you will be running Telligent Community. 

  1. Open the DNS Manager, navigate down to your domain.
  2. From the Action menu, select New Host (A or AAAA).  
  3. Enter just the portion of the subdomain before your main domain (so in our example of, we would enter demo).
  4. Under the fully qualified domain name, it will show you the corresponding full name of
  5. Enter the IP address for the server that will be running Telligent Community.

  6. Click Add Host.

Configure Exchange

To configure Exchange, you will need to create an Accepted Domains entry for Exchange will automatically route emails based on the DNS for the accepted domain. So in our example, when it receives an email for, it will find in the Accepted Domains list; look up the DNS entry for, and then forwards the message to that server via SMTP.

To add an accepted domain:

  1. Open the Exchange Management Console.
  2. Expand Organization Configuration from the side menu and select Hub Transport.  
  3. Go to the Accepted Domains tab to see a list of existing entries. 
  4. From the Actions menu or sidebar, select New Accepted Domain.  
  5. Pick a name for the entry.
  6. Set the Accepted Domain to the subdomain for Telligent Community ( in our example).
  7. Select the type of Internal Relay Domain.
  8. Click New for it to be created. The result should resemble the following screen shot.

     After updating, the list will refresh with the new entry:

Configure SMTP on the Telligent Community server

We usually recommend running default IIS Virtual SMTP server on the server where Telligent Community will be running in order to receive messages coming from the main Exchange server. By using the built-in SMTP server, it gains additional security options such as supporting SPA, TLS/SSL, and much more.

To install the SMTP server:

  1. Open the Server Manager.
  2. Navigate to Features and choose Add Feature.
  3. Select the SMTP Server feature. To manage the SMTP server, you will also need to ensure you have the IIS 6 Management Console installed from the Role Services for the Web Server (IIS) role.
  4. To configure it:
    1. Go to the Start menu.
    2. Under Administration Tools, choose Internet Information Services (IIS) 6.0 Manager
    3. Expand the sidebar and you will see SMTP virtual server.
    4. Open the server's properties by right-clicking it and navigating to Properties:
      • Ensure it is configured to use the IP address that we previously set up for the domain ( in our case).
    5. Next, go to the Domains item in the sidebar under the SMTP virtual server. The default entry likely corresponds to the computer's name. If it isn't the subdomain for Telligent Community, navigate to Action >  New > Domain.
    6. Create a new alias entry for the Telligent Community subdomain. This will allow it to receive email for both the default name, and the Telligent Community subdomain.

    7. Finally, open the Options on the default domain entry and take note of the Dropdirectorysetting. This is the location where the SMTP server will write all of the messages it receives, so this will be where Telligent Community reads messages.

Configure the Mail Gateway service for Telligent Community

Install the Telligent Community Mail Gateway following the normal instructions for Mail Gateway, but when configuring the mailgateway.config file, add an additional setting for readFromDirectory to the <Sites /> line. The entry should correspond to the drop directory setting that was configured in the SMTP virtual server.

It is also recommended that you adjust the pollMessagesInterval. This will set Mail Gateway to read the messages from the directory more frequently for a speedier response. The setting is in minutes, with the default being 5, but you can lower it to 1.

After finishing these steps, continue with the final configuration steps for Mail Gateway.