Configuring Dual Delivery

Once a sensor has been installed, you should now configure your email gateway(s) to direct a stream of messages to it (dual delivery).

The steps to configure dual delivery differ depending on your type of email gateway. See the dual delivery configuration guide for your email gateway.

Regardless of the gateway type:

  • Dual delivery should be configured to be from the "last hop" into your enterprise. Some enterprises have more than one gateway "tier" or layer of MTA (mail transfer agents) or SEG (secure email gateways); be sure that the dual delivery is configured to be from the final routing point, typically where you would send messages to your internal message store (like Microsoft Exchange).
  • Dual delivery should be configured to take place after all anti-spam, anti-virus, anti-malware, or any other filtering or sandboxing has occurred. Fortra Cloud Email Protection is not a first line of defense anti-spam, anti-malware replacement. Its purpose is to look for inauthentic messages that have cleared this filtering.

Interrupting Dual Delivery

There are two points at which messages from the sensor to Fortra Cloud Email Protection can be interrupted.

  • The sensor itself contains a “Receiving Mode” setting, which, by default is set to “Upload Data.”

    • If you need to test delivery to the sensor without uploading the data to Fortra Cloud Email Protection for processing, you can set the Receiving Mode to “Do Not Upload Data.”

  • Your organization has an “Ingest Mode” toggle which must be configured by your Fortra Cloud Email Protection sales engineer before messages will appear in Cloud Email Protection.

    • The “Ingest Mode” toggle is a safeguard Fortra Cloud Email Protection uses to protect against sudden spikes in traffic from new organizations sending data into the system.

Specific Dual Delivery Instructions

This guide has information about how to configure dual-delivery for the following environments: