xorlab NLU - xorlab

NLU stands for Natural Language Understanding. It classifies email into predefined topics, which you can search for and use in campaigns. For on-premises, the service is disabled by default.

Enable xorlab NLU for on-premises

Open the file activeguard/core/active_guard.yml in the Expert Editor.
Add a mltopic block to serviceProviders, and set the hosts to the same one as the existing ml service provider:

active_guard.yml

serviceProviders:
  mltopic:
    hosts:
      - https://ml1.de.activeguard.io
      - https://ml2.de.activeguard.io

topicService:
  enabled: true
  serviceProviderName: mltopic

In the Expert Editor, click Publish, then restart all MTAs. The serviceProviders and topicService settings in active_guard.yml require an MTA restart; see How to Activate the Configuration.

Configuration options

As an on-prem user, you can define which types of email traffic should undergo topic detection. To modify this behavior, adjust the following parameters in the local.properties file located at: activeguard/core/rule_sets/90_local/params/ in the Expert Editor. Set each parameter to ACTIVE or DISABLED as needed:

local.properties

EXECUTE_TOPIC_CLASSIFICATION_for_analysis_pipelines_state
EXECUTE_TOPIC_CLASSIFICATION_for_incoming_emails_untrusted_state
EXECUTE_TOPIC_CLASSIFICATION_for_incoming_emails_extended_state
EXECUTE_TOPIC_CLASSIFICATION_for_reported_emails_state

After changing these rule properties, click Publish. They become active within about one minute and do not require a restart.

The shipped defaults — which traffic is classified after activation, and how to limit topic detection to untrusted senders only — are documented in Detection Defaults → Topic classification. Access to that page is restricted.

⌘I

​Enable xorlab NLU for on-premises

​Configuration options

Enable xorlab NLU for on-premises

Configuration options