Home > Products > Exchange Connector > Getting Started with Exchange Connector

Getting Started with Exchange Connector

System Requirements

  • Microsoft .NET Framework 4.7.2 or later
    After installing the .NET Framework, we strongly recommend running Windows Update and installing the latest Important and Optional updates.
  • Microsoft Exchange Server 2019, 2016, 2013 with Mailbox Role, 2010/2007 with Hub Transport Role, or Exchange 2003
    The latest service pack for Exchange is recommended, as are multi-Role Exchange Servers. In an Exchange 2019, 2016 or 2013 environment, the Mailbox Role is required. In an Exchange 2010 or 2007 environment, the Hub Transport role is required.
  • Windows Server 2019, 2016, 2012 R2, 2012 or 2008 R2, SBS 2011 or Windows 7, 8.1 or 10
    Both 32-bit (x86) and 64-bit (x64) versions of Windows are supported. The operating system and platform architecture (32-bit or 64-bit) do not need to match if Exchange Connector is installed on a separate machine to Exchange. Desktop operating systems (Windows Vista, Windows 7, Windows 8 and Windows 10) are supported by Exchange Connector although installation on a server operating system is recommended.

    Exchange Connector does NOT need to be installed on the same machine as Exchange Server. Installing on a separate machine will be required for interoperability with Exchange 2003 or 2007 as these versions of Exchange do not support Server 2008 R2 or later.

    The latest service pack and updates for Windows are recommended. For Windows Server 2008 R2 and SBS 2011, a minimum of SP1 is required.

Note: Service Pack 1 is Required on Windows Server 2008 R2 & Small Business Server (SBS) 2011
The .NET Framework 4.7.2 requires Service Pack 1 on Windows Server 2008 R2 and Small Business Server (SBS) 2011. Exchange Connector installation will not proceed until the .NET Framework 4.7.2 or later has been installed.

The Service Pack 1 installer is the same for Server 2008 R2 and SBS 2011 and can be manually downloaded from the Microsoft Update Catalog (direct link) if necessary.

Installing Exchange Connector

Download the appropriate version for the platform you are using (32-bit or 64-bit).

Run the installer on the appropriate servers by clicking through the wizard. There are no installation options other than the destination folder.

Exchange Connector Setup Welcome

Configuring POP3 Accounts

Each POP3 mailbox to retrieve messages from needs to be added or imported.

POP3 Accounts

POP3 Account Details

POP3 Account Details

Special consideration should be given to the following settings:

  • Use Secure Connection (SSL/TLS)
    If the POP3 server is external to your network and it supports SSL or TLS (encrypted communications), using SSL is strongly recommended. Without using SSL, messages and potentially passwords are sent unencrypted.
  • Ignore Trust for SSL/TLS
    If the POP3 server uses a self-signed SSL certificate, you will need to select this option. If you are unable to connect to the POP3 server using SSL/TLS, try checking Ignore Trust for SSL/TLS.
  • Disable APOP Authentication
    If you cannot successfully login to the mailbox when clicking the Test button, try selecting the Disable APOP Authentication checkbox. APOP support is an enhanced security mechanism which should be used when SSL is not used. If SSL is used, APOP is not necessary and disabling it may improve performance slightly. This setting is required in cases where a POP3 server advertises APOP support when in fact it does not support APOP or does not support it correctly.
  • Leave messages on server
    If this option is not selected, messages will be immediately deleted from the POP3 server when they have been delivered to Exchange. If Leave messages on server is selected but Delete from the server after n day(s) is not selected, messages will never be removed from the POP3 server. Leaving messages on the server should not be enabled unless specifically required, as it will increase download time, because Exchange Connector must compare the ID of each message on the server with the list of message IDs that have already been downloaded. The more messages are left on the server, the longer this operation will take.
  • Connection Timeout
    This needs to be set with consideration to the largest possible messages which may be received, and the speed of the connection to the POP3 server (especially if it is over the Internet). In most cases the default of 10 minutes is sufficient.


Mailbox Details POP3 Server

Exchange Connector can use one of two methods for determining the recipients for messages downloaded from the POP3 server:

  • Each POP3 mailbox can be assigned to one or more Exchange recipients. That is, all messages are delivered to all of these recipients. This is the recommended approach.
  • Automatic recipient detection can be enabled. It is possible to have a single mailbox on the POP3 server for all users The final recipient of each message will be determined by Exchange Connector by analyzing the message headers. This approach has advantages and disadvantages and your environment needs to be considered carefully before selecting this approach.

Automatically Detect Recipients

Automatic recipient selection reduces the administration of maintaining individual mailboxes on the POP3 server. Two significant limitations of this approach may be encountered:

  • Bcc Messages may not be able to be delivered to the correct recipient
    When automatic recipient selection is used, Exchange Connector analyses the header of the message to determine the recipient. However, if the user was Bcc'd, their email address will not be included in the email header. Most email systems work this way for security, Bcc recipients are deliberately not shown in the header. Usually in this situation, Exchange Connector will deliver the message instead to the fallback recipient, which is selected using the option If the recipient cannot be detected, deliver to this recipient. If the message contains another recipient in your organization who is not Bcc'd (they are included in the To or Cc headers), Exchange Connector will have no way of knowing that the message was also intended to be delivered to another user via Bcc, and consequently they will never receive the message.

    Some POP3 servers are able to create a Bcc header in their copy of the message to avoid the above problem. If this option is available, it should be enabled. Additionally, some POP3 servers append an additional header, such as Delivered-To, which contains the address of the intended recipient, and also allows this problem to be worked around. Custom headers can be defined by clicking the button on the Recipients tab.

    A lot of spam also contains invalid headers, or a header without the actual recipient's address. In the absence of a special header being added by the POP3 server, these messages will also be delivered to the fallback recipient.
  • Catch all mailboxes on the POP3 server increase the volume of spam received
    A feature offered by some POP3 servers is a catch all mailbox, which collects all messages sent to a specific domain. This is often used in conjunction with automatic recipient detection. However, usually this results in the POP3 server not only accepting messages from trusted addresses, such as bob@domain.com, jane@domain.com, etc. but also unwanted addresses such as xyz@domain.com which are targeted by spammers who simply try every possible combination of characters at that domain. This can dramatically increase the volume of spam received. All of these messages will be delivered to the fallback recipient, which is selected using the option If the recipient cannot be detected, deliver to this recipient.

Some additional options are available when using automatic recipient detection:

  • Also Search the Received header
    For mail servers which do not support adding Bcc or other custom headers to the message, sometimes the recipient addresses can be determined by searching the Received header of the message. Unless you know the POP3 mail server supports either adding the Bcc header or another custom header, such as Delivered-To, it is strongly recommended that this option be left enabled. If the POP3 server supports adding custom headers, disabling the Received header search is recommended.
  • Also Search Custom Headers & Define Custom Headers
    Additional headers can be searched to attempt to detect recipient addresses. Delivered-To for example, is supported by Gmail. If your POP3 server supports a different custom header, it can be added using the Define Custom Headers button.

Undeliverable Messages

When recipients cannot be detected when using Automatic Recipient Detection, you can choose the delivery behaviour and configure a fallback recipient. These settings are not applicable when recipients have been manually selected.

POP3 Account Undeliverable Messages

Download Settings

These settings control general download settings which apply to all mailboxes.

  • Download Interval
    This setting controls the frequency with which POP3 mailboxes are checked for new mail. When a large number of mailboxes are set up, consideration needs to be given to the increased bandwidth consumption that will result from increasing the frequency (i.e. lowering the download interval).
  • Simultaneous downloads
    This setting controls the maximum number of mailboxes which Exchange Connector will download from simultaneously. For a more detailed explanation of this settings, see the knowledgebase article FAQ: How does the Maximum Outbound Connections Setting work?.

Download Settings

Configuring Exchange Server for Message Delivery

The configuration of Exchange Server depends on the version you are using.

With all versions of Exchange, care needs to be taken that anti-spam and anti-virus filters do not block messages delivered by QSS Exchange Connector to Exchange, unless the Delete the message permanently delivery setting is used (see discussion below). Failure to observe this will lead to messages permanently remaining on the POP3 server.

In Exchange 2003, the default configuration usually works with minimal changes. In Exchange 2007 and Exchange 2010, you may need to create a new Receive Connector. In Exchange 2013, it is recommended to create a separate Receive Connector specifically for Exchange Connector.

See the knowledgebase articles for detailed instructions:

Outbound message delivery (i.e. messages sent to external recipients outside your organization) is still handled by Exchange when using our POP3 connector. A simple way to configure outbound mail is to set Exchange to forward or "smart host" the mail through another mail server, such as your ISP's mail server. Instructions are provided for this configuration for the supported versions of Exchange:

Configuring Exchange Connector Delivery Options

SMTP Delivery

Ensure that the Exchange server name and SMTP port are correctly set on the SMTP Delivery tab. In Exchange 2007 and above, the port is defined in the Receive Connector in Exchange (see the knowledgebase article for instructions on configuring Receive Connectors). If Exchange Connector is not installed on the same machine as the Exchange Server messages should be delivered to, the Exchange Server name should be the fully qualified DNS name of the Exchange Server. If Exchange Connector is installed on the Exchange Server to forward messages to, the default value of localhost may be sufficient. If localhost does not work, firstly try using the fully-qualified DNS name of the server. Due do variations in DNS and IPv6 configuration, in some cases, it may be necessary to use an IP address instead of the server name. Only IPv4 IP addresses are supported.

Test the connection by clicking the Test button next to the Exchange server name on the Delivery tab of the options dialog. If an "unable to relay" error is displayed (as shown below), messages may appear to be delivered but it is highly likely that it will not work reliably and some messages may be left on the POP3 server. It is essential that the relay test is able to complete successfully.

SMTP Delivery

Folder Delivery

If you would like all messages stored in .EML format for archiving purposes in a specific folder, this option can be selected.

Undeliverable Messages

Additional delivery options are available to determine how messages which are rejected by Exchange should be handled.

  • Leave rejected messages on the POP3 server and attempt re-delivery
    This is the default option and should always be used until the configuration has been fully tested. If a message is rejected by Exchange, for example, by the spam filter, it will remain on the POP3 server. Using this option, anti-spam and anti-virus filters must be disabled or bypassed for the Receive Connector which is used by Exchange Connector. This is recommended where it is possible to do filtering on the POP3 server instead (which is strongly recommended).
  • Delete the message permanently
    The configuration must be tested before selecting this option to avoid the risk of losing messages due to incorrect Exchange relay configuration. This option is only used when anti-spam or other filtering which returns the 5550 5.7.1, 554 5.7.1 or 554 5.1.0 error codes in the SMTP session is used on the Exchange server to filter messages. Using this architecture, the original sender will not be notified that their message is rejected. In a POP3 connector environment, this is the only way to do anti-spam filtering on the Exchange server (which is why it is recommended to do it on the POP3 server instead).

Undeliverable Messages

Logging Options

Delivery Failure Reports

You can configure the administrator address to send delivery failure reports to, as well as whether Quantum Software Solutions receive error reports. The administrator email address must be a valid local mailbox on the Exchange server. Note that if message data is not included in delivery failure reports, failed messages will not be deleted from the POP3 server until the delivery issue is resolved.

SQL Server logging is primarily intended for diagnostic purposes with the assistance of Quantum Software Solutions support. Note that you must set up the database before enabling SQL Server Logging. There is a SQL script installed in the installation folder which needs to be run in SQL Management Studio or similar to create the database. See the knowledgebase article for full instructions.


Service Status & Alerts

The Service Status & Alerts tab shows the status of the Exchange Connector service, and recent event log messages generated by Exchange Connector. If the service is not running, a warning triangle will be displayed next to the Service Status & Alerts tab in the left pane.

Service Status & Alerts


If after performing the above steps messages are not delivered to Exchange recipients, see the knowledgebase article for troubleshooting instructions. For further assistance, contact Quantum Software Solutions support for further investigation. Setting up SQL logging may be of assistance. Detailed instructions can be found in this knowledgebase article.