Skip to main content
xorlab Security Platform can run in either of the following modes:
  • Monitoring: xorlab Security Platform is located out-of-band of the email flow and is only used to monitor the traffic (it cannot actively intervene). Usually, it receives the email traffic as an additional BCC recipient and all emails are dropped after processing. This mode allows email traffic monitoring with low impact on the infrastructure.
  • Inline: xorlab Security Platform is inline in the email flow and actively filters emails. This mode is configured whenever XSP is used for inbound email security. Emails are forwarded after they have been processed.
By default, XSP runs in inline mode. Have a look at the sections below if you want to configure either of the modes. After you finish configuring, please set up SMTP properly as described in Email routing.

Monitoring mode

The following changes are necessary to run xorlab Security Platform in monitoring mode:
  1. Open Expert Editor and navigate to the activeguard/core/active_guard.yml file.
  2. Under scanSources.handler, add the smtpOffline {} entry to the list and remove any existing entries named smtpInline {}.
  3. Under pipelineTypeConfig, set recipientRetrievalStrategy: MAIL_HEADER and envelopeFromRetrievalStrategy: HEADER:
    For M365 integrations, the value for the envelopeFromRetrievalStrategy key should be ENVELOPE_FROM.
    1. ENVELOPE_FROM in M365 integrations
  4. Under rules.params, add the monitoring_mode.properties entry as described in Profiles and change any DANA profile to monitoring_dana_offline_only.properties:
  5. Set up SMTP properly as described in Email routing.
  6. Disable delivery status notifications.
  7. Restart MTAs. For all MTAs, SSH connect to the MTA and execute:
This configuration sets xorlab Security Platform into monitoring mode. For more information about the envelope FROM and recipient configuration, please see the next section. It is possible to omit the handler block as it is set to smtpOffline {} by default:
Envelope-fromIt is important to provide xorlab Security Platform the original envelope FROM in monitoring mode. With the above configuration, XSP tries to parse the envelope FROM from any Received, Received-spf, and Return-path headers present in the email. Further possibilities are described in the next chapter.

Envelope FROM and recipient configuration

In monitoring mode, emails are often forwarded as copies (BCC) to xorlab Security Platform. In this case, it is possible that the SMTP envelope FROM and recipient information have been overwritten as a part of the BCC forward. The envelope FROM might be something like MAILER-DAEMON@gateway.internal and the envelope recipient is XSP itself like, for example, emails@activeguard.internal when the email arrives at xorlab Security Platform. Therefore, you need to configure XSP to get the envelope FROM and recipients from the correct location:
  1. ENVELOPE_FROM in M365 integrations
For M365 integrations, the value for the envelopeFromRetrievalStrategy key in pipelineTypeConfig.emails should be ENVELOPE_FROM.
Wrong configurationThe usual symptom of a wrong envelope FROM configuration is a missing or wrong envelope FROM shown in the detail view of an email in xorlab Control Center (XCC). Consequently, XSP cannot do various checks like, for example, SPF verification.
The following values are supported for envelopeFromRetrievalStrategy: The following values are supported for recipientRetrievalStrategy: You can also provide the original envelope FROM in a custom header. This header can then be specified in the following way:
It’s also possible to use regex to provide the original envelope FROM when you have multiple custom headers to check—just enter these headers without double quotes in a regular expression as the value for the envelopeFromHeaderName key:
The above expression matches either first or second header.

Disable delivery status notifications (e.g., bounce messages)

For monitoring mode, we recommend to generally disable delivery status notifications. This will make sure that xorlab Security Platform will never send delivery status notifications back to the sender when being in monitoring mode.
  1. Open the Expert Editor and navigate to the activeguard/mta/startup_cfg/postfix_custom/master.cf file.
  2. Find the three lines starting with bounce unix, defer unix, and trace unix, and set the last word on all three lines to discard:
  3. Open the activeguard/mta/startup_cfg/postfix_custom/main.cf file and comment out (e.g., using the Ctrl+/ or Cmd+/ keyboard shortcut) the delay_warning_time property (if you have multiple main.cf files, do it in each of them):
  4. Disable Delivery Status Notification (DSN) for bcc deployments in each main.cf file.

Inline mode

In inline mode, xorlab Security Platform is part of the email traffic and forwards emails accordingly. In order to activate it:
  1. Open Expert Editor and navigate to the activeguard/core/active_guard.yml file.
  2. Under scanSources.handler, add the smtpInline {} entry to the list and remove any existing entries named smtpOffline {}.
  3. Under pipelineTypeConfig, set envelopeFromRetrievalStrategy: ENVELOPE_FROM and recipientRetrievalStrategy: MAIL_ENVELOPE:
  4. Under rules.params, add the default_actions.properties entry as described in Profiles and change any Sandbox profile to default_dana.properties:
  5. Make sure that bounce messages are enabled in activeguard/mta/startup_cfg/postfix_custom/master.cf:
  6. Activate delivery delay notifications in activeguard/mta/startup_cfg/postfix_custom/main.cf:
  7. Set up SMTP properly as described in Email routing.
  8. Make sure to Publish the configuration changes in the Expert Editor.
  9. Restart MTAs. For all MTAs, SSH connect to the MTA and execute: