> ## 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.

# Automating Reported Messages Handling

When you want to automate the handling of reported messages, you can use the [Actions panel](https://docs.xorlab.com/9.0/actions-rules-and-profiles.md#actions-panel), although it gives just basic controls over what happens to the messages with malicious verdicts. For actions on a wider range of reported emails, you must resort to [campaigns](https://docs.xorlab.com/9.0/query-based-classifiers.md).

Campaigns are saved search queries empowered with actions: message action (what to do with the email—quarantine, deliver, or don’t do anything) and resolve action (what final verdict should be applied—benign, malicious, or none). Using smartly crafted campaigns, you can automate the way XSP handles reported messages.

> [!TIP]
>
> * Always check results in your environment first before activating the automation: perform search queries to see if they produce expected results, and when they do, create campaigns.
> * Start with [high-confidence spam and high-confidence phishing](https://docs.xorlab.com/9.0/search.md#verdict-confidences) auto-resolution.
> * Run queries in the **Abuse Mailbox / All Cases** view (an equivalent of `reported AND NOT(status:pending)`) to ensure only reported messages are processed.

The following examples show some ideas on how to automate with campaigns. They might not work well in every environment. Simply copy and paste the provided search queries and check their results.

* Resolve all reported messages with young domains (sender domain or embedded URL):

  `(#365daysoldsender or #365daysold) and (#spam or #phishing)`

* Resolve all reported messages with shortened URLs (all confidences):

  `#phishing #shortened`

* Resolve all reported internal emails without attachments:

  `#internal not #nolocalreputation not #document`

* Resolve all reported partner emails without attachments or links to cloud storage:

  `#partner #auth #trusted not #nolocalreputation not #cloudstorage not #document`

* Resolve all graymail without attachments or links to cloud storage:

  ` (#marketing or #crm or #newsletter or #bulk or #external) not #nolocalreputation not(#cloudstorage or #cloudstoragesender) not #document not #spffail not #dkimfail not #subjectcvip not #bodylt75words not #lowtrusted not #internal`

Hints:

* Use `not #nolocalreputation not(#cloudstorage or #cloudstoragesender)` to avoid any phishing false negatives.
* Use `not #document` to avoid any malware false negatives.

Please refer to [*Tags*](https://docs.xorlab.com/9.0/tags.md) to learn more about the tags used here.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.