> For the complete documentation index, see [llms.txt](https://docs.cipp.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cipp.app/user-documentation/email/administration/mailbox-rules.md).

# Mailbox Rules

This report lists the inbox rules configured on every mailbox in the selected tenant. Rules that forward, redirect, or quietly file mail are a common sign of a compromised account, so this is usually the first page to check during an investigation, and the one to sweep periodically across a whole estate.

## Table Details

| Column              | Description                                                                   |
| ------------------- | ----------------------------------------------------------------------------- |
| User Principal Name | The user principal name of the user's mailbox that the rule has been set for. |
| Name                | The name of the mailbox rule.                                                 |
| Priority            | The priority order of the rule. Rules run in this order, lowest first.        |
| Enabled             | A Boolean field indicating if the rule is currently enabled.                  |
| From                | The sender's information the rule applies to, if set.                         |

The row flyout shows the rule's full definition, which is where its actual conditions and actions are, including any forwarding or redirect target, the folder mail is moved to, and whether the rule stops further rules from running.

## Table Actions

<table><thead><tr><th>Action</th><th>Description</th><th data-type="checkbox">Bulk Action Available</th></tr></thead><tbody><tr><td>Enable Mailbox Rule</td><td>Enables the mailbox rule so it starts acting on mail again. Greyed out on a rule that is already enabled.</td><td>true</td></tr><tr><td>Disable Mailbox Rule</td><td>Stops the mailbox rule acting on mail while leaving it in place, so it can be turned back on later. Greyed out on a rule that is already disabled.</td><td>true</td></tr><tr><td>Remove Mailbox Rule</td><td>Deletes the mailbox rule. This cannot be undone, so disable a rule first if you may need to reinstate it.</td><td>true</td></tr><tr><td>More Info</td><td>Opens the Extended Info flyout with the full details for the selected row.</td><td>false</td></tr></tbody></table>

***

## Feature Requests / Ideas

We value your feedback and ideas. Please raise any [feature requests](https://github.com/CyberDrain/CIPP/issues/new?template=feature.yml) on GitHub.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.cipp.app/user-documentation/email/administration/mailbox-rules.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.