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

# Mailbox statuses

All the mailboxes monitored by Email Security are listed in `Email Security` > `Mailboxes`, with their protection status.

## Mailbox details

* **User**: the associated account owner.
* **Email address**: the exact monitored address.
* **Tenant**: the tenant linked to the mailbox.
* **Type**: `User` (personal mailbox, assigned to one person) or `Shared` (mailbox used by several people, with no single owner).
* **Suspicious emails**: the status of email analysis.
* **Compromised accounts**: the status of account takeover detection.

## Suspicious emails status

* **Active**: incoming and outgoing emails are being analyzed.
* **Inactive**: emails on this mailbox are not being analyzed. Hover over the status to see the reason, for example `Connection expired`, `Access revoked` or `Temporary sync issue`.

## Compromised accounts status

* **Active**: enough sign-in history to detect unusual account behavior.
* **Analyzing**: still gathering sign-in history. Detection is on, but not at full precision yet.
* **Dormant**: too little recent activity, so detection precision is reduced.

## Mailbox type

* **Microsoft 365**: pulled directly from the mailbox's configuration in Outlook (user or shared). If a mailbox shows an unexpected type, check its Outlook configuration.
* **Google Workspace**: a mailbox showing as `Shared` is usually a "Group" with individual mailboxes assigned to it, not an Outlook-style shared mailbox.

{% hint style="info" %}
For Google tenants, the user or shared type is only available from a recent change onwards: older data is not filled in. Microsoft 365 tenants have full historical data.
{% endhint %}


---

# 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.stoik.io/email-security/mailbox-statuses.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.