- 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.
Monitoring mode
The following changes are necessary to run xorlab Security Platform in monitoring mode:-
Open Expert Editor and navigate to the
activeguard/core/active_guard.ymlfile. -
Under
scanSources.handler, add thesmtpOffline {}entry to the list and remove any existing entries namedsmtpInline {}. -
Under
pipelineTypeConfig, setrecipientRetrievalStrategy: MAIL_HEADERandenvelopeFromRetrievalStrategy: HEADER:ENVELOPE_FROMin M365 integrations
-
Under
rules.params, add themonitoring_mode.propertiesentry as described in Profiles and change any DANA profile tomonitoring_dana_offline_only.properties: - Set up SMTP properly as described in Email routing.
- Disable delivery status notifications.
-
Restart MTAs. For all MTAs, SSH connect to the MTA and execute:
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 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:
ENVELOPE_FROMin M365 integrations
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.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:
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:
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.- Open the Expert Editor and navigate to the
activeguard/mta/startup_cfg/postfix_custom/master.cffile. - Find the three lines starting with
bounce unix,defer unix, andtrace unix, and set the last word on all three lines todiscard: - Open the
activeguard/mta/startup_cfg/postfix_custom/main.cffile and comment out (e.g., using the Ctrl+/ or Cmd+/ keyboard shortcut) thedelay_warning_timeproperty (if you have multiplemain.cffiles, do it in each of them): - Disable Delivery Status Notification (DSN) for bcc deployments in each
main.cffile.
Inline mode
In inline mode, xorlab Security Platform is part of the email traffic and forwards emails accordingly. In order to activate it:-
Open Expert Editor and navigate to the
activeguard/core/active_guard.ymlfile. -
Under
scanSources.handler, add thesmtpInline {}entry to the list and remove any existing entries namedsmtpOffline {}. -
Under
pipelineTypeConfig, setenvelopeFromRetrievalStrategy: ENVELOPE_FROMandrecipientRetrievalStrategy: MAIL_ENVELOPE: -
Under
rules.params, add thedefault_actions.propertiesentry as described in Profiles and change any Sandbox profile todefault_dana.properties: -
Make sure that bounce messages are enabled in
activeguard/mta/startup_cfg/postfix_custom/master.cf: -
Activate delivery delay notifications in
activeguard/mta/startup_cfg/postfix_custom/main.cf: - Set up SMTP properly as described in Email routing.
-
Make sure to
Publishthe configuration changes in the Expert Editor. -
Restart MTAs. For all MTAs, SSH connect to the MTA and execute: