> For the complete documentation index, see [llms.txt](https://docs.prventi.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.prventi.com/guides/getting-started/allowlisting-prventi-email-servers.md).

# Allowlisting Prventi email servers

Phishing attack simulations allowlist and configuration settings.

To ensure that Prventi's phishing simulation emails reach their intended recipients without being blocked by spam and phishing filters, it is essential for receiving email servers to allowlist Prventi's mail servers. Allowlisting helps establish a trusted connection between the sender and recipient, allowing our simulated phishing emails to bypass filtering mechanisms and provide an effective training experience for your team. By following the allowlisting instructions provided in our help documentation, you can ensure a seamless and reliable delivery of Prventi's phishing simulations, helping your organization improve its overall security awareness.

{% content-ref url="/pages/Ei7NysQDd7sMWwrRQY8L" %}
[Google Workspace Allowlisting](/guides/getting-started/allowlisting-prventi-email-servers/google-workspace-allowlisting.md)
{% endcontent-ref %}

{% content-ref url="/pages/sKuUrIX6QPj13JpwvbwN" %}
[Microsoft Office 365 Allowlisting](/guides/getting-started/allowlisting-prventi-email-servers/microsoft-office-365-allowlisting.md)
{% endcontent-ref %}

{% content-ref url="/pages/5Ct9ec3dvMp9xegnbMfg" %}
[Mimecast Allowlisting](/guides/getting-started/allowlisting-prventi-email-servers/mimecast-allowlisting.md)
{% endcontent-ref %}


---

# 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.prventi.com/guides/getting-started/allowlisting-prventi-email-servers.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.