> 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/mail-flow-statistics.md).

# Mail Flow Statistics

This page charts the selected tenant's mail flow over the last 7, 14, 30 or 90 days: how much mail arrived, how much of it was good, and how much Exchange Online stopped as spam, phishing or malware. A stacked bar chart breaks the dispositions down by day, a donut splits traffic by direction (inbound, outbound and intra-org), and two tables list the top mail senders and the top spam recipients.

## Action Buttons

<details>

<summary>Export Report</summary>

Generates a branded, client-ready PDF of the currently selected date range: an executive summary with a computed mail hygiene rating, the daily volume and disposition figures, the top senders and top spam recipients, and a set of recommendations drawn from that window's own data. A preview opens first, with a **Download PDF** button alongside it. Greyed out while the figures are loading, or when the tenant has no mail flow data for the selected period.

</details>

## Where the numbers come from

The daily disposition counts come from the Exchange Online `Get-MailFlowStatusReport` cmdlet, and the top sender and top spam recipient tables from `Get-MailTrafficSummaryReport`. Both support at most 90 days of history, which is why the period selector stops there.

{% hint style="info" %}
This page reports on a single tenant at a time, and is not available in All Tenants mode.
{% 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/mail-flow-statistics.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.