> For the complete documentation index, see [llms.txt](https://docs.fusion.vectra.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fusion.vectra.ai/detection-models/library/misconfiguration/outbound_imap_traffic.md).

# outbound\_imap\_traffic

Explanation This Netography Fusion Portal event monitors for cleartext outbound IMAP traffic, which should be discouraged due to security risks. IMAP is a protocol used for email retrieval and transfe

**Explanation**

This Netography Fusion Portal event monitors for cleartext outbound IMAP traffic, which should be discouraged due to security risks. IMAP is a protocol used for email retrieval and transfer, and the use of non-encrypted protocols like IMAP can expose sensitive information to interception and compromise.

**What to Look For**

To examine the results of the outbound\_imap\_traffic event, look for unencrypted IMAP traffic leaving the network or endpoint. This may indicate that users are accessing email accounts or sending messages without proper encryption or security measures in place. To remediate the issue, users should be encouraged to use more secure protocols like IMAPS or POP3S. Network administrators may also consider implementing security measures like email encryption and monitoring tools to ensure email traffic remains secure.


---

# 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.fusion.vectra.ai/detection-models/library/misconfiguration/outbound_imap_traffic.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.
