> 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/reports/mailbox-forwarding.md).

# Mailbox Forwarding

This report lists the mailboxes in the selected tenant that have forwarding configured, whether that forwarding points inside the organisation or out to an external address. Mailboxes with no forwarding are left out entirely, so anything appearing here is worth a look, and unexpected external forwarding is one of the clearest signs of a compromised account.

## Filters

Preset filters are available from the **Filters** button:

| Filter              | Shows                                                              |
| ------------------- | ------------------------------------------------------------------ |
| External Forwarding | Mailboxes forwarding to an address outside the organisation.       |
| Internal Forwarding | Mailboxes forwarding to another recipient inside the organisation. |

## Table Details

| Column                         | Description                                                                                                      |
| ------------------------------ | ---------------------------------------------------------------------------------------------------------------- |
| UPN                            | The user principal name of the mailbox that is forwarding.                                                       |
| Display Name                   | The friendly name of the mailbox.                                                                                |
| Recipient Type Details         | The kind of mailbox, for example `UserMailbox` or `SharedMailbox`.                                               |
| Forwarding Type                | `External` where an SMTP forwarding address is set, or `Internal` where the target is a recipient in the tenant. |
| Forward To                     | The address mail is being sent on to.                                                                            |
| Deliver To Mailbox And Forward | Whether a copy is also kept in the mailbox. Where this is `No`, mail is forwarded and nothing is retained.       |

Where a mailbox has both an external and an internal forwarding address configured, external wins in **Forwarding Type** and **Forward To**. The two underlying values are still reported separately as **Forwarding Smtp Address** and **Internal Forwarding Address**.

{% hint style="info" %}
This report covers forwarding set on the mailbox itself. Forwarding created by an inbox rule is not shown here, so a mailbox that looks clean on this page can still be forwarding mail through a rule.
{% endhint %}

***

## 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/reports/mailbox-forwarding.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.