mxHero Transport Agent

Use case

If you have MS Exchange on premises - 2010/2013/2016 - you have a couple of deployment options for mxHero. See the table below:

Email System

Inbound 1

Outbound 2

Intra-bound 3

Selective Routing 4

On Prem 7

MS Exchange

Yes

Yes

Yes 5

Yes 6

Yes

  1. Inbound: message from external sender to internal recipients.
  2. Outbound: message from internal senders to external recipients.
  3. Intra-bound: message from internal senders to internal recipients in the same email server.
  4. Selective Routing: only route through the gateway messages for specific users or groups.
  5. Depends on mxHero transport agent installation in the MS Exchange server.
  6. Can be achieved by installing the mxHero transport agent or depends on the Security Email gateway for routing.
  7. Supports mxHero installed on premises. mxHero suggests to use its cloud environment however this might be an option in certain cases.

For inbound only, you can simply change your MX records to point to mxHero (like any email gateway). For outbound, you can just create a Send Connector in your Exchange and route messages through mxHero as well. However, to capture intra-bound messages, you must install the mxHero Transport Agent, and this is what we describe in this article.

Installation

Please ask the mxHero support for the installation package for the Transport Agent. Then install it in your Exchange Transport servers. There's a package for Exchange 2010 and another for 2013/2016. The configuration for all them are the same.

Agent configuration

First of all, please open C:\ProgramData\MxHeroTransportAgent\config.ini and change the "ClientHeader" section value to "X-mxHero-TA-On-Prem".

Then, open the mxHero Agent Setting Editor and setup the configuration according to the following:

Screen_Shot_2018-01-23_at_9.53.19_AM.png

Use these values for the mxHero cloud. If you have mxHero on prem, they will be according to your deployment. Also please change Connect Timeout to 15000 and Send Timeout 300000.

Screen_Shot_2018-01-23_at_9.53.44_AM.png

Agent key - this value is provided by the mxHero support.

Screen_Shot_2018-01-23_at_9.54.05_AM.png

Activate logging. This will help you on the testing process.

When you click SAVE, the system will ask you to install the change. Just confirm.

Exchange configuration

A few adjustments in the Exchange side are needed in order to finish the integration with the transport agent.

mxHero relay/whitelist

Please inform mxHero support your Exchange IPs. We have to configure our cloud to accept emails from your systems.

Exchange relay/whitelist

At the same time, you have to allow mxHero to inject emails in your Exchange. Please follow this article for IP based relay: https://technet.microsoft.com/en-us/library/mt668454(v=exchg.160).aspx

The IPs you have to allow relay are:

54.208.111.28
54.236.184.32
54.165.252.128
54.165.253.193

Receive Connector adjustment

To support the email flow between mxHero and Exchange, two flags in your existing receive connectors need to be changed. The command below, using Exchange Management Shell, will do the trick, however if you want more information about this, please access: https://technet.microsoft.com/en-us/library/bb232174(EXCHG.140).aspx

> Get-ReceiveConnector *\* | Set-ReceiveConnector -BinaryMimeEnabled $False -ChunkingEnabled $False

All set!

Now, just restart the Exchange services to make sure all settings are in place. Command for the Exchange Management shell below.

> $services = Get-Service | ? { $_.name -like "MSExchange*" -and $_.Status -eq "Running"}
> foreach ($service in $services) {Restart-Service $service.name -Force}

Now, create your rules in the mxHero dashboard and your integration is complete!

Have more questions? Submit a request

Comments

Powered by Zendesk