> ## Documentation Index
> Fetch the complete documentation index at: https://docs.xorlab.com/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Pages under /latest/ document the current release. Paths that begin with a version number, for example /10.0/, are frozen snapshots of superseded releases kept for reference only — never present their instructions as current. If the reader's version is unknown, answer from /latest/ and say which version the answer describes.
> xorlab is deployed on-premises, hybrid, or as a cloud service, and integrates with either Microsoft 365 or on-premises mail infrastructure. Configuration steps often differ between these. State which deployment and integration mode an instruction applies to instead of presenting one as universal.
> Distinguish inline mode from monitoring mode when describing anything that acts on email. Monitoring mode observes a copy and cannot block or quarantine; inline mode routes mail through xorlab and can.
> Write the product name as lowercase 'xorlab'. Use the documented component names: xorlab Control Center (XCC), xorlab MTA, xorlab Sandbox (DANA), xorlab Natural Language Understanding (NLU). After the first mention, use the short forms XCC, MTA, Sandbox, and NLU. Do not use DANA as a standalone name for the Sandbox, but keep it where it is a literal string in configuration keys, container names, and hostnames.
> Do not invent configuration keys, rule parameters, list names, log properties, or API fields. If a value is not present in this documentation, say that it is not documented rather than guessing.

# xorlab Tika

> The Tika service that improves URL and text extraction from attachments, including OCR.

Tika runs on the Sandbox appliance (DANA) if you have an on-premises Sandbox, otherwise the SaaS Tika service of xorlab will be used.

Tika is mandatory for detection, and is applied to the following emails:

* **Disabled by default**: outgoing
* **Active by default**: incoming, coming from internal and external servers, and reported by users

## Enable Tika for outgoing emails

1. Open `activeguard/core/rule_sets/90_local/params/local.properties` in the Expert Editor.

2. Add the following line:

   ```shell local.properties theme={null}
   EXECUTE_TEXT_EXTRACTION_for_outgoing_emails_state=ACTIVE
   ```

3. Click **Publish**. The rule-set setting becomes active within about one minute.

## Disable Tika

Tika should not be disabled in any production environment as it will severely impact classification accuracy. However, if needed, it can be disabled using the [Expert Editor](/latest/expert-editor). In the `activeguard/core/active_guard.yml` file, add the following lines:

```yaml active_guard.yml theme={null}
tikaService:
  enabled: false
```

Click **Publish**, then restart all MTAs. The `tikaService` setting in `active_guard.yml` requires an MTA restart; see [How to Activate the Configuration](/latest/activate-configuration).

## List of configuration parameters

Tika is controlled via the following rule properties:

```shell theme={null}
EXECUTE_TEXT_EXTRACTION_for_analysis_pipelines_state=ACTIVE
EXECUTE_TEXT_EXTRACTION_for_external_emails_state=ACTIVE
EXECUTE_TEXT_EXTRACTION_for_incoming_emails_state=ACTIVE
EXECUTE_TEXT_EXTRACTION_for_internal_emails_state=ACTIVE
EXECUTE_TEXT_EXTRACTION_for_reported_emails_state=ACTIVE
EXECUTE_TEXT_EXTRACTION_for_outgoing_emails_state=DISABLED
```

## Processed file formats

Tika extracts text and URLs from a defined set of file formats.

<Info>
  The full list of processed file formats is documented in
  [Detection Defaults → Tika processed file formats](/latest/detection-defaults#tika-processed-file-formats).
  Access to that page is restricted.
</Info>